I think it is the order the BIOS discovers/lists the cards. We have
some SuperMicro MBs where each boot the drivers may be loaded in a
different order. Then ethX moves around and we are not happy campers.
The new naming has been a very good thing for us as our systems reboot
at least once a day. The kernel naming is not usable as it is not
consistent across boots.
On Tue, Mar 3, 2015 at 8:18 AM, Per Jessen
Andrei Borzenkov wrote:
One reason for inventing new names was avoiding name clash with automatic kernel assignment. This still applies.
Yes, I remember reading that as part of the reasoning.
If you do not like "predictable" names (I do not) use something like netXX. But do not use ethXX, as it puts you back on square one.
Which is where I want to be :-)
The only case when it is sure to work is when your names are the same as autossigned by kernels, in which case you can simply leave it to kernel in the first place.
I think in fact my names (ethXX) are always the same as those allocated by the kernel. Sofar I have never had any problems with names clashing. I guess "simply leave it to kernel" means using net.ifnames=0 ?
Just wondering out loud - surely the loading sequence of the network drivers is important too? On one system I see 'e1000' loaded first, followed by 'tg3'. e1000 is for a 4port gigE card, tg3 is for two builtin gigE interfaces. My renaming makes the two tg3 interface = eth0, eth1 and the e1000 eth2-3-4-5. If I had left it to the kernel, I guess I would have e1000 = eth0-1-2-3 and tg3 = eth4-5.
-- Per Jessen, Zürich (3.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org