Bug 43969 – pcmcia starts net.eth1, but not dhcpcd

• Product: Gentoo Linux
• Status: RESOLVED WONTFIX

[Description Bjarke Istrup Pedersen (RETIRED) 2004-03-07 10:08:18 UTC]

I have pcmcia added to the boot runlevel, and it starts net.eth1, but for some reason it does not start the dhcpcd daemon.
I have waproamd running, since eth1 is a wireless card, the problem is that before I upgraded waproamd it did wait for eth1 to come up before it moved on with the rest of the booting, but now it does not start dhcpcd, and just moves on.

It happend as I upgraded waproamd.

Reproducible: Always
Steps to Reproduce:
1. emerge waproamd pcmcia-cs
2. rc-update add waproamd boot, rc-update add pcmcia boot
3. plug in network card and power up the machine.

Actual Results:  
It does not wait for the wireless system to get up before moving on, which 
causes it not to start dhcpcd.

Expected Results:  
It should wait for the wireless subsystem to get running, and then start 
net.eth1

[Comment 1 Bjarke Istrup Pedersen (RETIRED) 2004-03-08 02:06:45 UTC]

Related to: #44013 

[Comment 2 rob holland (RETIRED) 2004-07-16 09:15:59 UTC]

Please provide relevant conf.d/net lines.

[Comment 3 Bjarke Istrup Pedersen (RETIRED) 2004-07-16 11:48:02 UTC]

Well, it works now, guess it was a problem with an older version of baselayout.

[Comment 4 Henrik Brix Andersen 2004-08-18 13:07:14 UTC]

Suggest closing this bug as NOTABUG.

[Comment 5 Bjarke Istrup Pedersen (RETIRED) 2004-08-18 16:58:35 UTC]

Hmm, since wireless-config seems to be gaining ground, and net.ethX has changed dramaticly, it is likely that waproamd will be obsolete for gentoo within the next few months if all goes well.
I will leave it open for a while, in case something turns up.

[Comment 6 Peter Johanson (RETIRED) 2004-08-19 06:22:28 UTC]

wireless-config is no replacement for waproamd. They behave very differently. (I'm not trying to pass judgement on one or the other, but just point out that calling waproamd obsolete is not really fair).

Anyway, marking WONTFIX.