On Wed, 26 Jul 2006 00:38:49 -0400, Walter Dnes wrote: > Thanks Daniel and Louis. With "nofirewire" the boot messages showed 2 > eth devices, but the real ethernet chip now comes up as eth0, which is > what I wanted.
You can use udev rules to ensure your network interfaces are correctly
named, which saves disabling anything. On the other hand, if you will
never use Firewire networking, you could simply remove the option from
your kernel.
The udev rules I use to ensure my wired, wireless and Firewire interfaces
are named i that order are
KERNEL=="eth*", SYSFS{address}=="00:0d:93:3c:76:26", NAME:="eth0"
KERNEL=="eth*", SYSFS{address}=="00:0d:93:ef:f2:c0", NAME:="eth1"
KERNEL=="eth*", SYSFS{address}=="00:0d:93:ff:fe:3c:76:26", NAME:="eth2"
Those are the MAC addresses of the interfaces.
--
Neil Bothwick
And all the Borg left was this copy of Windows...
signature.asc
Description: PGP signature
