Jesse Brandeburg wrote:
On 4/24/06, Rick Jones <[EMAIL PROTECTED]> wrote:
The udev stuff runs after the device has already chosen it's default name.
It has to, it's part of the hotplug infrastructure, and we don't want
to depend on usermode to define the name. Just choose some other
convention "eth_0" or something like that.
Is that because adding another NIC at a later time might cause it to
grab ethN out from under what I'm trying to do with udev?
From what I read its likely to be because there may already be a
device named "eth1" due to default naming when you are trying to
rename a device (say eth0) to eth1.
this is all because Debian now has async init, right?
Beats me. I got the impression that udev things were happening "early
enough" in my case that I didn't run into the issue. still, init and
device names are presently a maze of twisty passages to me. someone else
also suggested not using the ethN stuff - or at least not starting at 0,
but start them at N where N is reasonably large. i decided to call them
lan0, lan1, etc just to be perverse and see what breaks.
BTW, since the letters in udev are all hex, it shouldn't matter
whether they are upper or lower case, IMO
that would be my opinion as well, certainly that was my expectation -
that I could simply "cut and paste" MAC addresses from the likes of
ifconfig output
alas, it seems that if I leave theme upper case, the renaming does not
happen. i am _guessing_ the comparison is a simple string compare. and
it doesn't _really_ know that what is being compared is a MAC address?
rick jones
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
