On Tue, Jul 8, 2014 at 3:01 PM, Mark Tinberg <mtinberg at wisc.edu> wrote: > >> And more to the point, /usr isn't supposed t be needed until you are >> past the point of mounting all filesystems so you can boot from >> something tiny. Doesn't modprobe need its files earlier than that? > > This work is all about being able to boot a system with just a read-only /usr. Any foo you need to get to a complex filesystems, like NFS or encrypted software RAID needs to be in the initial ramdisk which the boot loader can access before the kernel loads and which tools like Dracut build based on what’s required for your particular setup. The seeds of that change basically existed from the time that initial ram disks were introduced as a feature a long time ago, now we’ve just widely acknowledged this reality. Errr, I thought you only needed stuff on the ramdisk to access the root partition. Can't you mount /usr from a different disk controller or NFS from modules loaded from /lib/modules? Or was that already broken when user's home directories were kicked into /home? And if not, how did things get in that mess? -- Les Mikesell lesmikesell at gmail.com