On Tue, Nov 01, 2005 at 10:24:05PM +0100, Sven Luther wrote: > On Tue, Nov 01, 2005 at 09:03:37PM +0100, Erik van Konijnenburg wrote: > > On Tue, Nov 01, 2005 at 06:02:57PM +0100, Jonas Smedegaard wrote: > > > On Mon, 31 Oct 2005 19:52:52 -0700 Vagrant Cascadian <[EMAIL PROTECTED]> > > > wrote: > > > > On Sun, Oct 30, 2005 at 11:51:11PM +0100, Jonas Smedegaard wrote: > > > > > Currently, MOUNTDIR does not support nfsroot so needs to be > > > > > commented out completely. > > > > > > > > ugh. > > > > > > Well, actually... Looking at FsEntry.pm and other code it might actually > > > be supported somehow - or support is halfway there... > > > > It's recognised as something we can't support. Mounting eg > > 'www.debian.org:/boot' would require name resolution, and there's way > > too much guesswork involved in doing that on the initial boot disk: > > do you want /etc/hosts? LDAP? NIS? DNS? There's other unpleasantness > > involved in trying to interpret nfs partitions from fstab on the boot > > image, but this is the most obvious one. > > What about runing host www.debian.org and using the returned IP address ?
What about round-robin DNS, changes in hosting, IPv6 addresses, NFS over IPsec tunnels, gateways other than the default, using an old server without warning after the hostname was changed to a new IP address ... It's possible to generate an NFS image using such heuristics that may occasionally work, but I don't know how to do it reliably. Under those circumstances, it would be misleading to interpret an NFS path in fstab and pretend that we expect it to work. On the other hand, the current approach with ip= allows very precise control, from fully automatic IP configuration using DHCP to fully manual. That said, there's room for improvement to the manual; it also could make sense to have a custom config file and wrapper script for common NFS configurations such as used in lessdisks. Regards, Erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
