> It turns out that this is a problem in discover: more recent versions > reorder modules such that via-rhine comes after ieee1394 networking, > making it eth1 instead of eth0, but all that the user sees is that > networking no longer works. [...] > I consider this breakage because it requires /etc/network/interfaces to > be rewritten for the different eth numbers under different kernels (2.4 > without firewire and orinoco puts the wired NIC at eth0, 2.6 puts it at > eth2), particularly with static addresses. A consistent order with say > all of the hard-wired NICs first, wireless second, and firewire last > would clear this up.
This is a case of local misconfiguration, not a bug in discover. There is no guarantee that network interfaces are assigned the same name by the kernel from occasion to occasion. The name can be different after modules are unloaded and reloaded; it can be different after reboot; it can be different after changing kernel version or discover version. It is wrong to expect such a guarantee. 'eth0', etc., are just temporary handles that allow the same devices to be accessed again and again so long as they exist. It happens often to be the case that the same devices end up getting the same handles on boot but it is wrong to demand that this always be the case. If you want a name that is associated always with the same physical device then use the ifrename utility to create such a name. -- Thomas Hood <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
