Marco wrote :
>
> ifrename is not needed if you are using udev. If you are not, you are on
> your own.
Sorry, but that's not true. It pains me that the hotplug/udev
project suffers from NIH, this is not the first time I see them making
blanket statements that their stuff completely replace the old stuff
when it's not (yet) the case.
udev doesn't understand much about networking (that is not its
job) and therefore is lacking critical functionality when it comes to
renaming network interfaces. Just one simple example : udev can't
distinguish between the two network interfaces created by the Aironet
driver for each card, and therefore will give them the same name.
Yes, udev is nice and work for 95% of the cases. For the
remaining 5%, you really need ifrename. As ifrename handles 100% of
the cases, I personally would not waste any time with udev for network
interfaces, and rather would work at better integrating ifrename in
the udev/hotplug framework. Note that by the time you fix udev to
handle all the subtelty of network interfaces, you will have the
perfect clone of ifrename ;-)
Have fun...
Jean
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
