udev-110 ->111 changed behaviour for naming net-devices?

Bryan Kadzban bryan at kadzban.is-a-geek.net
Mon May 21 15:22:07 PDT 2007

Jens Stroebel wrote:
> I am aware that I could force eth1 onto the device with an udev-rule 
> like the above for eth0, but would like to avoid this if at all
> possible.

It's not possible.  ;-)

With the current udev setup, udev will write rules for *all* NICs, to
give them all stable names (by MAC address by default).  If you only
create a single renaming rule, udev should create the rest for you.

The reason it's set up this way is that device scanning and module
loading both happen in parallel, so all NICs can be assigned any name.
Say the device that you want to call eth1 comes up as eth0 instead, and
the device that you want to call eth0 comes up as eth1 (because they get
loaded in the other order).  Say the udev rules run after both devices
get named.  In this situation, you *have* to have rules to rename *both*
devices, otherwise udev will hang your booting process for a long time.
When the device that's currently eth1 tries to rename itself to eth0,
udev will try to wait until eth0 isn't in use -- but if your rules never
rename the device using eth0 to eth1, that wait will never finish.

But if you remove all your rules and reboot, udev will generate new
rules for all your NICs, so Alexander's suggestion of removing them all
is a good idea.  Just beware that what you want isn't possible.

(Why do you want it, by the way?)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
URL: <http://lists.linuxfromscratch.org/pipermail/lfs-dev/attachments/20070521/b9d9fc97/attachment.sig>

More information about the lfs-dev mailing list