On Mon, 2009-06-22 at 17:31 -0400, Warren Togami wrote: > I just realized that the following are yet another NFS syntax variation. > > client_test "NFSv3 root=nfs DHCP path only" 52:54:00:12:34:00 \ > "root=nfs" 192.168.50.1 -wsize=4096 || return 1 [snip] > When is it ever necessary to use explicitly root=nfs or root=nfs4 > instead of root=dhcp? It seems functionally equivalent while > unnecessarily limiting since DHCP should tell you the protocol. Sigh. Let's have this conversation again. The kernel nfsroot support allows root=/dev/nfs to get the root path information from DHCP instead of nfsroot. We support that legacy syntax. root=nfs was a shortcut to root=/dev/nfs root=nfs4 was a shortcut to root=/dev/nfs4, which is something I made up when adding nfsroot support to dracut, as it seemed to have a certain symmetry with the kernel's support for NFSv3. You were planning on removing root=nfs, root=nfs4, and root=/dev/nfs4, leaving only root=/dev/nfs for compatibility with the kernel, so the root=nfs tests would need to be converted to root=/dev/nfs and the rest would go away in that case. > Benefits of de-supporting these variations: > * Simplify the documentation further, fewer possible ways to configure > it to confuse people. Have a standard syntax section that only mentions the way we want to have people use the software, and have a Legacy (and possibly Expert) section that gives other ways that work, with a note that these are not the suggested/preferred ways. Am I missing something that makes this so hard? Or do I just have a kinder opinion of users than others around here? -- 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
