Broken NFS server (or client?)
Mark Street
jet at sonic.net
Wed Aug 8 22:16:39 PDT 2001
Aha, from your previous post let's look at the parameters being passed.
>The appended lines are:
>root=/dev/nfs
>nfsroot=192.168.0.6:/
How about adding
ip=dhcp
It should work with dhcp though, the kernel should start a dhcp/bootp query
when it boots as you are using kernel level autoconfiguration.
At 10:04 PM 8/8/2001 -0700, Lincoln Peters wrote:
>>Hmmm, this has me wondering....are you using..... ip=<autoconf> for the
>>kernel parameter . Do the NIC's initialize with proper IP settings on both
>>ends?
>
>As far as the network goes, I know that the server is working because I
>have been administrating it mostly using SSH (it is currently living on a
>garage workbench where there are no chairs). I'm not sure about the
>client because I can't find any evidence that it is actually getting on
>the network, even though the problem is being reported as an NFS error.
>
>I suppose that the problem could reside in the DHCP client that's built
>into the kernel. I have tried manually assigning IP information at the
>LILO prompt (ip=192.168.0.217), but the documentation is so cryptic, I'm
>not sure if I'm doing it right or not.
>
>This is just a wild guess, but should I try using a BOOTP or RARP server
>instead?
More information about the talk
mailing list