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. Instead, pass ip= and nfsroot= on the kernel command line as documented in kernel tree Documentation/nfsroot.txt. Do not pass "root=" on the kernel command line. /init ignores it, but perhaps it confuses the kernel. The most common form is ip=eth0 or ip=all, with nfsaddr= omitted. This will do DHCP initialisation of ethernet device, and get mount point over DHCP in the usual manner. What happens if you omit ip= depends on your config file: you could use a hard disk instead, or start an ssh deamon, or simply panic. More variations possible that can be expressed in a simple command yaird command line option. You may want to remove IP addresses from all your network cards, then run "/usr/lib/yaird/exec/ipconfig ip=all" to get a feeling for what the IP client code does. Patches for the manual page are welcome. Regards, Erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
