Originally Posted by Nylex
This isn't really a major problem, but I'd like to get rid of those messages anyway. They look a bit out of place!
I recently installed Slack 10.2 on a new hard drive and the first thing I needed to do was install NDISWrapper, so that I could get online. I did that and after having some problems, I could get an IP address via DHCP from our router. Then, I added two lines to /etc/rc.d/rc.local (as I had done in Slack 10.1):
The next time I started my machine, I saw a message saying something like "only rc.inet1 can call rc.wireless" (I can't remember the exact wording) and it said to try "/etc/rc.d/rc.inet1 wlan0_start" instead. I replaced the first line of rc.local with that and rebooted. That worked fine and I could get online. When I went to shutdown/reboot again, I received the aforementioned message about dhcpcd not running. I thought this would be solved by commenting out the second line in rc.local, but this did nothing and I still get those messages.
Edit: the lines for wlan0 that I've uncommented in rc.inet1.conf appear below.
Starting with Slackware 10.2 the "rc.wireless" script depends on some configuration work in the rc.inet1 script, and it can no longer run on it's own. But you corrected your addition in rc.local, so no problems there.
However, you should not really have to add "/etc/rc.d/rc.inet1 wlan0_start
" in rc.local because Slackware will execute that exact command during booting. With your 4 lines for rc.inet1.conf as shown above you're all set to go. The oly thing I remember about ndiswrapper is that you manually have to load the module because hotplug will not do that for you. You would have to add this line to the bottom of /etc/rc.d/rc.modules
As for those "**** /sbin/dhcpcd: not running
" messages, they are harmless. They occur when you configured a network interface to use DHCP, but then
- the interface did not get a network connection
- the DHCP client determined that it received an IP address with infinite lease time
In both cases, the dhcpcd program that started for such an interface while booting, will terminate itself. When you finally shutdown the machine, Slackware looks for DHCP configured interfaces and tries to terminate the DHCP client program (dhcpcd) that it expects to still be running. In those cases where the dhcpcd has already terminated, you will see your error message.