Linked by Hadrien Grasland on Tue 25th Jan 2011 14:23 UTC, submitted by Debjit
Fedora Core "Fedora developer, Matt Domsch, has announced that Fedora 15 is breaking the conventional ethX naming scheme used for Ethernet devices by adopting a new scheme called Consistent Network Device Naming."
Thread beginning with comment 459646
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Why?
by phoenix on Tue 25th Jan 2011 21:04 UTC in reply to "RE[4]: Why?"
phoenix
Member since:
2005-07-11

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.


BIOS updates from Tyan have a tendency to toggle the default value of this item. We've been bitten by it several times.

Same with Debian kernel upgrades that toggle the order PCI buses are enumerated. We've also been bitten by this several times.

Neither of those are "OUROWNSTUPIDFAULT".

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.


Yeah, I mentioned that in another post. And sent a question to the original blogger about it, to see how it works in that situation.

Further, how difficult is to sudo rm /etc/udev/rules.d/70-persistent-net.rules?


It's one extra (manual) step in our restore process. Not too ornerous, but still a pain.

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.


We do that a lot, to work around the brokeness.

Reply Parent Score: 2