client hangs after eth0 becomes ready

[Carsten Aulbert]

Hi all

On Wednesday 16 November 2011 08:21:26 Carsten Aulbert wrote:
> Specifying eth0 will not help as the kernel "arbitrarily" changes the names
> upon reboot. The machine I'm currently struggling with is choosing eth0 for
> the first on-board NIC for ~50-60% of the time (no hard numbers on that
> one) and the first add-on NIC otherwise (currently only these two are
> connected).
> 
> I think it highly depends on timing when the kernel is scanning for
> available devices. As long as you only have NICs handled by a single
> driver/module I think you are fine, but add different cards into the same
> machine and you will run into trouble...

I'm just about to dive into this issue now.

Is there some "working" code already, incorporating the BOOTIF/ip information 
into scripts/live-premount/select_eth_device?

And more importantly, is there an easy way to debug initrds without continuous 
reboots and set-x / echo?

Cheers

Carsten