Public SourceMage Discussion List

[Thomas Orgis <thomas-forum AT orgis.org>]

Am Sun, 18 Jun 2006 09:49:00 +0200
schrieb Pieter Lenaerts <e-type AT sourcemage.org>:

> could this discussion be put on the list to avoid half or conflicting
> solutions?

OK, I'll try to recapitulate:

1. I have two network interfaces on my workstation: onboard tulip and
intel eepro100 pci card.
2. I wanted the intel card to be eth0 as I configured externel networking
for this interface.
3. Reboot keep changing the order of the interfaces, kernel autoloading
the drivers before anything else can happen.
4. Thus, I've set the MAC fields in /etc/sysconfig/network/eth[01] to
the hardware macs of the respective card, expecting them to be named
according to mac.
5. That didn't work - biggest effect was that the mac of the tulip card
was changed to that one I've set for the intel card...
6. After some fiddling with alternate udev rules, we actually figured out
that renaming to "intel" and "tulip" instead of "eth0" and "eth1" works.

My conclusion: The device renaming to eth0/1 fails because there is already
a device present with that name (since kernel brought up both drivers
before the udev rules for sysconfig are executed).
I have now the devices "intel" and "tulip" with the netconfig approach
and am happy with the persistent order (these names are better anyway... I
could even go retro Tru64 and name them "ee0" and "ewa0";-).

Juuso also thought about the mac2name script working right / the execution
for both network card events interfering with each other.
I now asked if he has some update on this...


Thomas.

Attachment: pgpMh5DGkqDQQ.pgp
Description: PGP signature