-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 15/07/12 09:00 PM, Maxim Kammerer wrote: > On Mon, Jul 16, 2012 at 3:30 AM, Duncan <1i5t5.dun...@cox.net> > wrote: >> Thinking in that direction does stimulate yet another idea, tho. >> What about a squashfs root? AFAIK squashfs is read-only at use >> time, thus enforcing actually mounting something else to write >> anything, eliminating many of the down sides of sticking with the >> initial ramfs root, but it would allow the same flexibility in >> terms of sticking whatever into it at create-time, while only >> taking the memory necessary for what's actually stuck in it at >> create-time. > > It is possible, see: > https://github.com/mkdesu/liberte/blob/master/src/root/initrd/init > https://github.com/mkdesu/liberte/blob/master/src/etc/fstab > > The setup above is somewhat different from what you have in mind > (SquashFS image is located on disk, and contains the complete live > filesystem, not just a skeleton), so mounting read-writable > branches can be deferred to the regular post-initramfs services > (such as localmount) — on the other hand, maybe you want to do the > same (mount branches read-only in initramfs, and remount them > read-write in an init.d service). >
...if going this route, why not simply not bother to pivot_root out of the initramfs at all? or pivot_root but only into a directory structure still sitting in the initramfs? As long as all non-root bits are in separate storage, you can mount 'em all in the appropriate place... -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlAEHNAACgkQ2ugaI38ACPCbBgD+MCInpuQXjir37zFTn3ebJe30 dEWqqxihYox1+XrR7JYA/26jjkglGXZzxP0Kq17xuyoDBD8qnymAsziieDsMCMvN =/C5P -----END PGP SIGNATURE-----