dhclient-script NFS errors with busybox ifconfig
John Faith
jfaith at freescale.com
Tue Apr 11 20:19:42 UTC 2006
Tim,
I ran across this after my initial post:
http://marc.theaimsgroup.com/?l=dhcp-client&m=105405904626026&w=2
, so it makes sense that nothing works after the address changes. I
guess I assumed that a new address would be obtained from the server
before changing the current one.
I also got another suggestion to change the 'ifconfig $interface 0 up'
to 'ifconfig $interface up' in dhclient-script, or wrap it in an 'if',
which is how some Redhat systems do it.
I think it makes sense just to try a non-NFS filesystem.
Thanks,
John
Tim Peiffer wrote:
> I can't address the busybox ifconfig, but I would check you path.. edit
> line 94 from
> ifconfig to /sbin/ifconfig or whatever. /*/sbin is usually never in the
> path.
>
> Regards,
> Tim
>
> John Faith wrote:
>
>>Hello!
>>
>>I am trying to use dhcp-3.0.3b1 on an embedded Linux board (kernel
>>2.4.20) with a NFS root filesystem. The 'ifconfig' on this system is
>>from busybox 1.01.
>>
>>When I run 'dhclient' as root, I get NFS errors and my filesystem goes
>>away. I've tracked it down to line 94 in dhclient-script (which is the
>>same in dhcp-3.0.4b3.tar.gz):
>>
>> ifconfig $interface 0 up
>>
>>I can run 'ifconfig eth0 0 up' by hand, and it completes without
>>printing an error, but subsequent commands fail due to the NFS
>>filesystem going away.
>>
>>Has anyone else run into this with busybox ifconfig, or know if this is
>>a dhclient-script bug or a busybox bug?
>>
More information about the dhcp-users
mailing list