With this patch, /boot will be mounted read-write on boot with the disk initramfs script.
We're still in a very broken situation in that /boot/rootfs.img is loop mounted to build the unionfs, and so if the ext3 in /dev/sda1 (/boot) ever needs fscking, we wont be able to do so because it will be in use for /...
22:57 < lool> So hmm the concept of /boot/rootfs.img is fundamentally flawed in
that you need /boot mounted to write new kernel images to it
(e.g. security updates) but if you ever have a fs check to run on
it, you can't because rootfs.img is loopback mounted for the unionfs making the /
22:57 < lool> You need read-write and accessible, and you can't fsck it from /
With this patch, /boot will be mounted read-write on boot with the disk initramfs script.
We're still in a very broken situation in that /boot/rootfs.img is loop mounted to build the unionfs, and so if the ext3 in /dev/sda1 (/boot) ever needs fscking, we wont be able to do so because it will be in use for /...
22:57 < lool> So hmm the concept of /boot/rootfs.img is fundamentally flawed in
unionfs making the /
that you need /boot mounted to write new kernel images to it
(e.g. security updates) but if you ever have a fs check to run on
it, you can't because rootfs.img is loopback mounted for the
22:57 < lool> You need read-write and accessible, and you can't fsck it from /