В Tue, 18 Jun 2013 21:55:15 +0200
Per Jessen
Anton Aylward wrote:
We've been though this before , such as when we made /dev/ 'dynamically generated'. It didn't fit everyone's needs right away. (I'm not sure it does even now.)
Right now all I see in in rules.d/77-network.rules which uses ifup/ifdown and rules.d/70-persistent-net.rules which maps an Ethernet address to eth0
YMMV - it probably does :-)
Don't hold your breath, in 13.1 we're headed toward socalled "PredictableNetworkInterfaceNames", such as enp13s0, enp14s0, enp3s1f0, enp3s1f1, enp6s2 ...
It will be a bit more complicated than that ... those predictable interface names are defined for PCI attached devices only. There is nothing for other classes of devices. So at one side we do not have old method to shuffle the names around anymore, on the other hand we also do not have any persistent names generated automatically. You still can rename them, of course, just make sure it will not clash with kernel auto-generated names.
https://bugzilla.novell.com/show_bug.cgi?id=820589
Speaking professionally, we have some 50+ openSUSE systems spanning 10.2 to 12.2. They are all SNMP monitored, locally and externally. The change of network device naming introduced by systemd (yes, this IS a systemd issue), will mean our systems will be unable/unlikely to move beyond 12.3. I am hoping the openSUSE comm^H^H^H^H do-ocracy will see sense and at least retain the ability to rename devices automagically as we are used to. Maybe we can take over some stuff from upstream SLES.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org