Quote:
Originally Posted by Carmelocotonto
Ok, I will try this afternoon or tomorow. A similar question: you has wrote this:
Programs included (not exhaustive): firefox, geany, xterm, uxterm, gnome-terminal, mate-panel, x11vnc, feh, idle3.8, python3, obconf, pcmanfm, nautilus, vim, nano, htop, onboard
Installable via apk (package manager), including, but not limited to: gcc, g++, clang, qmake, falkon, midori, epiphany
What is the difference?. If I install Falkon, will it dessapear when I restart because KoBox runs in a chroot jail, which means it is (mostly) hidden the Koboˋs root filesystem?
|
No, essentially:
There are three partitions on the eMMC/MMC:
/dev/mmcblk0p1 # rootfs
/dev/mmcblk0p2 # recoveryfs
/dev/mmcblk0p3 # onboard
Here's the essential of the mounts at boot:
/dev/mmcblk0p1 : / (root)
/dev/mmcblk0p3 : /mnt/onboard
KoBox is a disk image R/W that you can add/modify things on. I think that on the one I uploaded, you have about 800MB of free space when you start.
This disk image is mounted like this:
/mnt/onboard/.adds/kobox/kobox.img : /mnt/user
So no, unless it's specific circumstances, a chroot jail is writable, like your hard disk. It's like a Linux system in another Linux system.
If you install Falkon, it won't touch anything of your /mnt/onboard partition, and it will only install in /mnt/user. You can always return to Nickel by rebooting the device:
And uninstalling KoBox is as easy as deleting the disk image (mostly, you can delete NickelMenu and KFMon if you really want to also). That's one great advantage of chroots; all is containerized.
Though I still recommend you to make a backup before you try this.