On 19/08/14 17:32, Felix Miata wrote:
On 2014-08-19 07:40 (GMT-0400) Robert Schweikert composed:
Felix Miata wrote:
Used to be if you wanted eth0 to be eth0 you could put one of the following in /etc/udev/rules.d/: -rw-r--r-- 1 root root 228 Oct 10 2013 70-persistent-net.rules (-> eth0) -rw-r--r-- 1 root root 0 Oct 4 2013 80-net-name-slot.rules -rw-r--r-- 1 root root 0 Oct 4 2013 80-net-setup-link.rules Now it seems the only way is via net.ifnames=0, which used to be necessary only during installation. Is this a temporary problem? Does something need to be configured in /etc/wicked now to avoid cluttered cmdlines? The device naming is systemd related, Surprise, surprise, surprise. :-p
i.e net.ifnames=0 disables predictable network device names (http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface...). Ancient news. As you quoted, I've been using it during installation for many many moons. I just didn't notice until last night, because YaST would automatically include installation cmdline parameters in the default bootloader stanza (if not others), that it was the only way that worked, that all the content in /etc/udev/rules.d/ was being ignored. It was by accident last night that a stanza lacking it got used last night, whereupon something during init announced the renaming of eth0 to some longer gobbledegook.
Note too that same URI mentions 80-net-setup-link.rules as 2 of 4 different options, though only for udev 209+.
Of course one can argue about the interpretation of predictable ;) The new ways are all predictable - they produce results that:
1-rarely (if ever) use the most used name everyone familiar with networking got used to at the beginning of their networking lives. 2-rarely match between any two (or 3, or 4, or ...) machines that didn't come off the same assembly line. BTW I have bug #889307 open against wicked with requested input added. I removed /etc/udev/rules.d/70-persistent.net which causes a problem.
"wicked convert /etc/sysconfig/network >network.xml" "mv network.xml > /etc/wicked/ifconfig/", when network starts up it says it's skipping use of this file for a higher priority config file but doesn't say what. Found I still needed /etc/sysconfig/network/ifcfg-* files in place to have the network configured. Renamed /etc/sysconfig/network/routes to /etc/sysconfig/network/ifcfg-routes to get the default route configured. Remaining question is why it's skipping network.xml. I haven't got around to running the individual commands suggested. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org