hi all, I just received some suggestions from the dhcpcd's author. I guess it could be the right moment to review dhcpcd section in the "Network Configuration" paragraph in CRUX Handbook. --nico Begin forwarded message: Date: Fri, 03 Feb 2012 17:45:35 +0000 From: Roy Marples <roy@xxx.name> To: acrux <acrux@xxx.it> Subject: Re: dhcpcd uses clang if available on the system and it's not always good on linuxppc On Thu, 2 Feb 2012 12:35:33 +0100, acrux wrote:
[...] (CRUX main project uses dhcpcd as default)
I just checked your init script for dhcpcd.... May I make some recommendations? /sbin/dhcpcd -t 10 -h $HOSTNAME eth0 ... /usr/bin/killall -q /sbin/dhcpcd May I recommend this instead? /sbin/dhcpcd -t 10 ... /sbin/dhcpcd -x Firstly, when invoked like that it runs in master mode and handles the situation where you have more than one interface a lot better. Like say a laptop and wired and wireless both connected (and maybe a 4G phone) and dhcpcd will handle routing and DNS correctly, preferring by default wired > wireless > 4G When stopping with -x, the call will spin until dhcpcd has exited, which may or may not be important if the user has defined any hooks that must be called before spinning down the disks. Lastly, is crux using dhcpcd-dbus and dhcpcd-ui(gtk) for a system tray notification of dhcpcd state? Thanks Roy -- GNU/Linux on Power Architecture CRUX PPC - http://cruxppc.org/