- How do I mount mini_fo?
- Why does mini_fo create these weird "META_dAfFgHE39ktF3HD2sr" in my storage directory?
- How can I overlay the root file system?
- But how can I really overlay the root file system (for the whole system)?
- After overlaying the root file system /proc, /sys, /dev or any file system mounted on the old root disappears!
- I get "permission denied" messages when trying to modify files via mini_fo, although ls -l shows sufficient privileges!
mount -t mini_fo -o base=<base directory>,sto=<storage directory> <base directory> <mount point>yes, it is silly to have to specify the base directory twice, I hope to fix this soon. See below for some examples.
# mount -t mini_fo -o base=/,sto=/tmp/sto/root / /mnt/mini_foNow change your root file system to the mini_fo mount point:
# chroot /mnt/mini_foNow you've got a shell with a mini_fo overlayed root file system.
/etc/bootinitwith something like this:
insmod /lib/modules/mini_fo.o mount -t tmpfs none /tmp mkdir /tmp/sto mount -t mini_fo -o base=/,sto=/tmp/sto / /rw cd /rw mkdir old_rootfs pivot_root . old_rootfs exec /usr/sbin/chroot . /sbin/init echo "Oops, exec chroot didnt work! :( :( :( " exit 1then included
init=/etc/bootinitin the kernel boot parameters line. It worked like a charm (never saw the Oops message, though :o) -- RicardoScop - 30 Jun 2005
After overlaying the root file system /proc, /sys, /dev or any file system mounted on the old root disappears!This is normal behaviour. mini_fo only overlays the file system that was specified as base. It can't "detect" other file systems that are mounted somewhere on the base, so these mountpoints will be empty. The solution is to simply mount file systems you want to overlay to their appropriate mount points in the overlaid root file system before chroot'ing. For above example (assuming the file system mounted on /home is a seperate partition):
# mount -t mini_fo -o base=/,sto=/tmp/sto/root / /mnt/mini_fo
# mount -t mini_fo -o base=/home/,sto=/tmp/sto/home/ /home/ /mnt/mini_fo/home/
# mount -t sysfs sys /mnt/mini_fo/sys/
# chroot /mnt/mini_foNote that sysfs is mounted directly. I don't think it would make much sense overlaying such a file system with mini_fo.
This is usually caused by insufficient privileges in the storage filesystem. Check that the user accessing the overlaid file system has privileges to modify the storage directory.
"permission denied" messages when trying to modify files via mini_fo, although
ls -l shows sufficient privileges!
-- MarkusKlotzbuecher - 07 Jun 2005