>> Warren Togami wrote: >> > >> >> A question: Why not use root=/dev/nfs and the other options according to >> kernel doc, like nfsroot=... and ip=autoconf? For me that is much more >> readable. > > It is a matter of taste and historical contingency, I suppose. The > current nfsroot mounting stuff was added way before initramfs/initrd was > an option, and it was probably easier to not mess up the in-kernel root= > handling code (which expected a device to mount). I think it is important to keep backwards compatibility in this specific case, and handle "root=/dev/nfs" kind of stuff. Really, think about keeping 2, 3 different cmdlines depending if the system is newer or older. It may look like a small hassle, but getting this right sometimes takes some time Since initramfs > handles all that stuff now (assuming you are using it, of course), the > kernel neither knows nor cares about the contents of the root= > parameter, and we do not have to be bound by its restrictions. We can > make (for example) root=192.168.10.2:/my/root/path do The Right Thing > and mount that as an nfs filesystem. We would still handle the other > case, of course. Sometimes it does care. Even thougheverybody uses initrds today, theoretically we should be able to use only the kernel (think really tiny system, embedded systems, etc) -- - Thiago Galesi -- To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
