Guus Sliepen wrote: > > I haven't responded to this bug, because there was some discussion at > that time about ifrename, hotplug and udev, but forgot about this bug > afterwards. Anyway, hotplug at some point ran ifrename itself, and > people are saying that hotplug and/or udev will do the renaming itself. > Is #312070 still an issue for you? If not, I will close this bug.
Yup, I had more problems with ifrename and hotplug: On my notebook I had a kernel with the ethernet-over-IEEE1394 module, which creates a new eth device. Even when inserting the module for the regular ethernet device before starting hotplug etc., it inserted the IEEE module, which shifted the ethernet device from eth0 to eth1 and made itself eth0. I therefore configured ifrename to call any device driven by the IEEE module fire* . This works sometimes, it seems to be a timing problem. Sometimes after boot the IEEE is fire0 and ethernet is eth0, as expected. But sometimes IEEE remains eth0, because between module insertion and device renaming the eth0 is already taken up and then can't be renamed anymore. This caused me that much headache and problems that I ended up in compiling my kernels without ethernet-over-IEEE support. So that problem is not solved yet. regards Hadmut -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
