On Tue, Nov 01, 2005 at 11:37:02PM +0100, Erik van Konijnenburg wrote: > On Tue, Nov 01, 2005 at 10:38:56PM +0100, Jonas Smedegaard wrote: > > Erik: Would it make sense to allow static IP, and only choke on non-IP > > value before the colon in fstab? > > Finding the server would be easier. Now to figure out a way to decide > whether client should have a hard-coded IP address or a DHCP address. > For bonus points, do so in a distro independent manner... > > I couldn't find a way to do so reliably. a few points: first, i never suggested getting the root path from /etc/fstab, only that if there was a line in /etc/fstab that identifies that it is a nfs root, i.e.: foo:/some/path / nfs defaults,ro,nolock 0 0 in the vast majority of cases, a line like this would indicate that it's an NFS Root. exactly what to do with that information is another story, but it seems like enabling some sort of NFS Root configuration would be reasonable. second, just because it's impossible to generate an NFS Root perfectly for every possible permutation of NFS Root network setup doesn't mean it wouldn't be wise to implement some way to enable NFS Root that will work in some (if not many) situations. if the behavior and limitations were well documented, and there was a simple way to disable it, it would seem like a good route to go. thirdly, commandline options should override initramfs build-time values, just like the built-in kernel NFS Root handling. fourthly, why not only support nfsroot if root=/dev/nfs is passed on the commandline, just like built-in kernel NFS Root handling? live well, vagrant
Attachment:
signature.asc
Description: Digital signature