Hi,

I had the same problem as described in http://www.linuxquestions.org/questi...h-12.2-691316/ (with my eth0 one and only network card not getting up properly on startup) and didn't get it to work. I thought about upgrading the dhcpcd package - and did that, which resolved the problem so far. My network card gets an IP again during the boot process with the 3.1.8 version of dhcpcd.

BUT: I noticed that there are so many newer newer dhcpcd releases, that I wonder if there any serious caveats. Is there any special reason why Patrick still uses the dhcpcd which is installed with 12.2? Any big problems known?

Thanks,

tito

I'm not sure I see the connection between the problem and the solution, but oh well.

About dhcpcd, it's one of those cases of "if it's not broken, then why fix it?" for the most part. Of course, you have a counterpoint, so I guess someone has to get off their ass now :-)
The main reason the 2.x version was bumped in 12.2 was that I had troubles with the earlier 2.x release, but the newer one fixed it. Rather than deal with potential incompatibilities in the 3.x series, and since 2.0.8 fixed what I was seeing, 2.0.8 was good enough.

Anyway, we'll investigate the 3.x series and see what it breaks.

Hi Robby,

many thanks for your reply. If can help with some information I would be pleased to do so, please let me know.

3.1.8 is working here with Slackware 12.2 and with eth0 (nVidia Corporation CK804 Ethernet Controller, rev. 3 - driver: forcedeth) and wlan0 (Bus 001 Device 006: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter - driver rtl8187). eth0 got an IP with only DHCP set to yes in rc.inet1.conf. wicd got an IP for the wlan-stick when I tried it manually.

tito

Yep, dhcpcd 2.0.x also didn't work for me anymore. Updating to 3.2.3 fixed it.

Robby, many thanks again for the update in Slackware-current