On Wednesday 16 April 2008 10:31:13 am John Summerfield wrote: > Jarod Wilson wrote: > > On Wednesday 16 April 2008 05:55:32 am John Summerfield wrote: > >> I don't want to assign an IP address in the kernel commandline, so it > >> has to get one. > >> > >> At present, it doesn't do this, so netconsole doesn't work. > >> > >> Just for the hell of it, I added "ip=dhcp" as one does for nfs-root. > >> > >> Then, netconsole failed. After that, the kernel used dhcp to get an IP > >> address. > >> > >> Now, if the kernel could get the IP address first, then netconsole would > >> work and I'd be able to log this problem without fiddling around with > >> serial cables and other computers. > > > > At first blush, I'm assuming this falls down because there isn't a dhcp > > client built into the kernel. For nfs root, the dhcp client is actually > > in the initrd, and I'm guessing netconsole wants to start up even before > > the initrd has been unpacked. > > No, the kernel (if so built) doesn't require an initrd. This worked as > far back as 2.2, maybe earlier. It might once have only done bootp, but > it's had dhcp for years and years.
Sorry, I wasn't clear, I was speaking purely in the Red Hat kernel case, where CONFIG_IP_PNP is not set. Of course, re-reading with the context of me talking about new things that may be enabled in post-F9 rawhide, I'm guessing you were already aware of this, and were perhaps suggesting that it be enabled as well... -- Jarod Wilson [EMAIL PROTECTED] _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
