| |||||||||||||
Domsch: Consistent Network Device Naming coming to Fedora 15Domsch: Consistent Network Device Naming coming to Fedora 15Posted Jan 26, 2011 23:20 UTC (Wed) by dlang (✭ supporter ✭, #313)In reply to: Domsch: Consistent Network Device Naming coming to Fedora 15 by foom Parent article: Domsch: Consistent Network Device Naming coming to Fedora 15
I agree, that's why I have this disabled on all my debian systems.
just using the ports in detection order has proven to be _ar_ more reliable over time. the only thing I have to do is when I deploy a new kernel, I have to test it on a lab box first to make sure it didn't reorder anything (and guess what, I have to do that anyway to make sure that there aren't other problems with the kernel). I've been through a few cases where the order has changed, and it hasn't been nearly the problem that I've had with the 'tie to a MAC address' approach.
(Log in to post comments)
Domsch: Consistent Network Device Naming coming to Fedora 15 Posted Jan 28, 2011 12:37 UTC (Fri) by nix (subscriber, #2304) [Link]
What problem has tying to a MAC address given you? It should only cause problems if you change MACs all the time, and who does that?
Domsch: Consistent Network Device Naming coming to Fedora 15 Posted Jan 30, 2011 15:47 UTC (Sun) by rwmj (subscriber, #5474) [Link]
Welcome to the world of virtualization :-)
70-persistent-net.rules is a constant source of trouble when V2V-ing, migrating and cloning virtual machines.
In any case, the change mentioned in this article has nothing to do with udev's persistent naming, and all to do with how the network interfaces are named when you first install an OS. It's a reasonably sensible change, although given that this driven from the BIOS, there is plenty of room for BIOS vendors to fsck things up as they normally do.
Rich.
|
|||||||||||||