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