Joshua Kwan wrote: > On Fri, Jul 16, 2004 at 04:17:41PM +0200, Josselin Mouette wrote: > > When several ethernet devices are available, the name of the device is > > not a reliable way to identify it. For example, when booting d-i on my > > laptop, the firewire port was detected as eth0 and the 100baseT one was > > detected as eth1. At the time of reboot, hotplug identified eth0 as the > > 100baseT and eth1 as the firewire, and the network stopped working. > > > > This could be solved by identifying adapters by their MAC address; > > ifupdown allows that using external scripts, but it isn't a builtin > > function. There may be other solutions, but that's the only idea I can > > think of. > > I think this was a problem with hw-detect that Joey fixed already. > Joey? Yes, I've fixed this particular case. hw-detect has to completly mirror the boot up sequence and bring up the same interfaces in the same order, which is generally fragile and sucky though. I'd like to see us use something like nameif in the future to avoid these problems, but how to make it work with things like pcmcia I don't know. -- see shy jo
Attachment:
signature.asc
Description: Digital signature