On Mon, 14 Jul 2003, James Tison wrote: > Can't think of a way to push the status of the TCP/IP stack, but I can pull > one: > I thought of another. It also gets it up early;-)
You need a custom kernel, configured so as to be able to mount its root filesystem with NFS. Documentation/nfsroot.txt has the full details. You need to build a custom kernel in which you turn on the IP layer autoconfiguration code, and with your custom kernel, boot with these parameters: root=/dev/nfs nfsroot=[<server-ip>:]<root-dir>[,<nfs-options>] ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf> Your kernel needs to have support for the relevant NIC built in, not loaded as a module. When the stack initialises, your DHCP server logs the event (if you're using DHCP), and when the filesystem gets mounted immediately after, that's logged too. There is another way to mount a root filesystem. I've done it, but I've not seen it documented. Its advantage is that it works with a standard kernel. You need an initial ramdisk, and in that you have a linuxrc that loads the network card's driver, initialises it with ifconfig and then mounts the root filesystem. This has the same logging facilities as the previous method. -- Cheers John. Join the "Linux Support by Small Businesses" list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb Copyright John Summerfield. Reproduction prohibited.
