To view parent comment, click here.
To read all comments associated with this story, please click here.
Looking at the naming scheme, it will fail with something as simple as changing the direction that PCI buses are enumerated by the BIOS.
Boot with "Descending" selected in the BIOS, and the top PCI slot on a desktop is bus 0. Boot with "Ascending" selected in the BIOS, and the top PCI slot is now bus 4.
Thus, your PCI NIC will change from pci0#0 to pci4#0.
Yeah, that's consistent.
Ok, seriosuly - how often does that really happen? If you're changing the order in which PCI devices are enumerated, such a bug resulting from that would be labelled YOUROWNSTUPIDFAULT.
Also, I would point out that the scheme presented by fedora would also be vulnerable to that; it relies on the enumeration provided by the BIOS.
Further, how difficult is to sudo rm /etc/udev/rules.d/70-persistent-net.rules ? And, the current system allows sysadmins to force a device to a particular ethX name; one can override the system and make a device eth1 instead of eth0. Fedora's system seems ot provide no such flexibility.





Member since:
2007-04-06
But most systems already do this automatically. Check out your /etc/udev/rules.d/70-persistent-net.rules
It seems to me that Fedora has come up with a more complicated solution to an already-solved problem. A minor, but needless additional fragmentation of Linux user space consistency.