[opensuse-factory] wicked wicked, again
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 wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/19/2014 02:08 AM, 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, i.e net.ifnames=0 disables predictable network device names (http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface...). Of course one can argue about the interpretation of predictable ;) Later, Robert - -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead Public Cloud Architect rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJT8zejAAoJEE4FgL32d2UkofgIAKZLOX4bRK9CXcEMREjfICfG PSRqvWoQRm76WXFvlxiu7ssj0WYk+0JS2gZ6Ss0T1nRusNP/hcDfPeKnM4zm9+ia tU9jr2Xj2h8FfFk+FvIPfMy5XJlb6oaMR+MGTZYrKt0c4+6e6s+jiCp7haxL9Z63 8xH369MV29lHRzCvEftlKx8jNhwKsngnJkr4o1QfgmbHZwwyZ+Sgcdhjhc27Dso6 Jk3SIZFyR1OYEVC8Dt2h8Rm4GuXIBV68bC8E6A1sU66lLTvNYOsY0KtqeQv9+8Iz 6sEtQHWFdI9kUqaOw4PLznFBi6Saa6zP9L3ZaHZzUsE42bphIGP9aNZIw5GUVag= =cIj8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 19/08/14 a las #4, Robert Schweikert escribió:
The device naming is systemd related, i.e net.ifnames=0 disables predictable network device names (http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface...). Of course one can argue about the interpretation of predictable ;)
Yes, there is however one more possible condition in upcoming kernel versions http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=68... udev will not rename interfaces that the kernel marks as NET_NAME_PREDICTABLE or interfaces that were already named by userspace OR the ones already renamed. No kernel driver uses this feature as of yet, however. -- Cristian "I don't know the key to success, but the key to failure is trying to please everybody." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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
On 2014-08-20 00:07 (GMT+0100) Sid Boyce composed:
BTW I have bug #889307 open against wicked with requested input added. [ https://bugzilla.novell.com/show_bug.cgi?id=889307 ] 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.
On host gx27c that I was having init complete leaving route missing, I purged /etc/udev/rules.d/, kept net.ifnames=0 on cmdline, and rebooted to find eth0 happily working as expected, but also a freshly created /etc/udev/rules.d/70-persistent-net.rules. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 20/08/14 01:25, Felix Miata wrote:
On 2014-08-20 00:07 (GMT+0100) Sid Boyce composed:
BTW I have bug #889307 open against wicked with requested input added. [ https://bugzilla.novell.com/show_bug.cgi?id=889307 ] 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. On host gx27c that I was having init complete leaving route missing, I purged /etc/udev/rules.d/, kept net.ifnames=0 on cmdline, and rebooted to find eth0 happily working as expected, but also a freshly created /etc/udev/rules.d/70-persistent-net.rules. These are the names I saw originally and only lo was configured. I had to change the names, e.g ifcfg-eth0 changed to ifcfg-enp3s0:- # wicked ifstatus all wicked: Ignoring config /etc/wicked/ifconfig/network.xml because of higher prio config lo up link: #1, state up type: loopback config: compat:/etc/sysconfig/network/ifcfg-lo leases: ipv4 static granted leases: ipv6 static granted addr: ipv4 127.0.0.1/8 addr: ipv6 ::1/128
enp3s0 up link: #2, state up, mtu 1500 type: ethernet, hwaddr 50:e5:49:c8:2e:8c config: compat:/etc/sysconfig/network/ifcfg-enp3s0 leases: ipv4 static granted addr: ipv4 192.168.2.201/24 enp5s6 up link: #3, state up, mtu 1500 type: ethernet, hwaddr 00:1c:f0:5b:65:5a config: compat:/etc/sysconfig/network/ifcfg-enp5s6 leases: ipv4 static granted addr: ipv4 192.168.10.10/24 route: ipv4 default via 192.168.10.103 wlp0s22f2u4u4u2 up link: #4, state up, mtu 1500 type: wireless config: compat:/etc/sysconfig/network/ifcfg-wlp0s22f2u4u4u2 leases: ipv6 dhcp granted I now see, it's ignoring /etc/wicked/ifconfig/network.xml and using /etc/sysconfig/network/ifcfg-* but without them only lo gets configured. 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
On 20/08/14 01:50, Sid Boyce wrote:
On 20/08/14 01:25, Felix Miata wrote:
On 2014-08-20 00:07 (GMT+0100) Sid Boyce composed:
BTW I have bug #889307 open against wicked with requested input added. [ https://bugzilla.novell.com/show_bug.cgi?id=889307 ] 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. On host gx27c that I was having init complete leaving route missing, I purged /etc/udev/rules.d/, kept net.ifnames=0 on cmdline, and rebooted to find eth0 happily working as expected, but also a freshly created /etc/udev/rules.d/70-persistent-net.rules. These are the names I saw originally and only lo was configured. I had to change the names, e.g ifcfg-eth0 changed to ifcfg-enp3s0:- # wicked ifstatus all wicked: Ignoring config /etc/wicked/ifconfig/network.xml because of higher prio config lo up link: #1, state up type: loopback config: compat:/etc/sysconfig/network/ifcfg-lo leases: ipv4 static granted leases: ipv6 static granted addr: ipv4 127.0.0.1/8 addr: ipv6 ::1/128
enp3s0 up link: #2, state up, mtu 1500 type: ethernet, hwaddr 50:e5:49:c8:2e:8c config: compat:/etc/sysconfig/network/ifcfg-enp3s0 leases: ipv4 static granted addr: ipv4 192.168.2.201/24
enp5s6 up link: #3, state up, mtu 1500 type: ethernet, hwaddr 00:1c:f0:5b:65:5a config: compat:/etc/sysconfig/network/ifcfg-enp5s6 leases: ipv4 static granted addr: ipv4 192.168.10.10/24 route: ipv4 default via 192.168.10.103
wlp0s22f2u4u4u2 up link: #4, state up, mtu 1500 type: wireless config: compat:/etc/sysconfig/network/ifcfg-wlp0s22f2u4u4u2 leases: ipv6 dhcp granted
I now see, it's ignoring /etc/wicked/ifconfig/network.xml and using /etc/sysconfig/network/ifcfg-* but without them only lo gets configured. Regards Sid.
Those results was some weeks ago and there have been many updates to wicked since. I moved /etc/sysconfig/network to / on one box and rebooted - it's all good. sabre:~ # wicked ifstatus all lo up link: #1, state up type: loopback config: /etc/wicked/ifconfig/network.xml leases: ipv4 static granted leases: ipv6 static granted addr: ipv4 127.0.0.1/8 addr: ipv6 ::1/128 enp8s0 up link: #2, state up, mtu 1500 type: ethernet, hwaddr 54:04:a6:32:0b:3c config: /etc/wicked/ifconfig/network.xml leases: ipv4 static granted addr: ipv4 192.168.10.21/24 route: ipv4 default via 192.168.10.103 route: ipv4 192.168.2.0/24 via 192.168.10.2 wlp0s19f2u3 up link: #3, state up, mtu 1500 type: wireless config: /etc/wicked/ifconfig/network.xml leases: ipv4 dhcp granted leases: ipv6 dhcp granted addr: ipv4 192.168.1.3/24 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
В Tue, 19 Aug 2014 02:08:01 -0400
Felix Miata
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)
Name of file does not matter as long as it sorts early enough. If it really sets interface name, it should win. If not, it is a bug.
-rw-r--r-- 1 root root 0 Oct 4 2013 80-net-name-slot.rules
This file does not exist.
-rw-r--r-- 1 root root 0 Oct 4 2013 80-net-setup-link.rules
So which one do you have?
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?
How is it related to wicked at all? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2014-08-19 12:10 (GMT-0400) Andrei Borzenkov composed:
÷ Tue, 19 Aug 2014 02:08:01 -0400 Felix Miata composed:
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)
Name of file does not matter as long as it sorts early enough. If it really sets interface name, it should win. If not, it is a bug.
It's the exact same file that worked in 12.3 and 13.1. How would it not really be setting the interface name?
-rw-r--r-- 1 root root 0 Oct 4 2013 80-net-name-slot.rules
This file does not exist.
??? it may have no content, but it's still a file, same as one of same name that is a symlink to /dev/null/.
-rw-r--r-- 1 root root 0 Oct 4 2013 80-net-setup-link.rules
So which one do you have?
All three.
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?
How is it related to wicked at all?
Used to be ifup on single NIC, wireless-free, fixed IP systems simply worked. Now Wicked messages cross my init screen instead, so presumably it's responsible to see to it that I have functional networking. As I did not at time of OP, what more logical to suspect than the supplanter? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
В Tue, 19 Aug 2014 19:05:07 -0400
Felix Miata
On 2014-08-19 12:10 (GMT-0400) Andrei Borzenkov composed:
÷ Tue, 19 Aug 2014 02:08:01 -0400 Felix Miata composed:
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)
Name of file does not matter as long as it sorts early enough. If it really sets interface name, it should win. If not, it is a bug.
It's the exact same file that worked in 12.3 and 13.1. How would it not really be setting the interface name?
Please show full content (without comments).
-rw-r--r-- 1 root root 0 Oct 4 2013 80-net-name-slot.rules
This file does not exist.
??? it may have no content, but it's still a file, same as one of same name that is a symlink to /dev/null/.
This file does not exist in udev package so creating empty file to hide it does not serve any purpose.
-rw-r--r-- 1 root root 0 Oct 4 2013 80-net-setup-link.rules
So which one do you have?
All three.
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?
How is it related to wicked at all?
Used to be ifup on single NIC, wireless-free, fixed IP systems simply worked. Now Wicked messages cross my init screen instead, so presumably it's responsible to see to it that I have functional networking. As I did not at time of OP, what more logical to suspect than the supplanter?
You could simply ask instead of making statements. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2014-08-20 06:16 (GMT+0400) Andrei Borzenkov composed:
Please show full content (without comments).
Suffice to say there's a difference between 13.1's and the one auto-generated by 13.2. The latter adds to the last line the following: ATTR{dev_id}=="0x0"
You could simply ask instead of making statements.
The statements I made provided context for the questions that followed. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 19.08.2014 um 08:08 schrieb Felix Miata:
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?
Interface naming has nothing to do with wicked / networkmanager. It's all done by udev. And you should know that after all these years. https://bugzilla.novell.com/show_bug.cgi?id=868375 Udev rules are ignored by initramfs. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2014-08-20 12:35 (GMT+0200) Stefan Seyfried composed:
Interface naming has nothing to do with wicked / networkmanager. It's all done by udev. And you should know that after all these years.
I may know how it was, but with the changes implemented by the likes of KMS, Systemd and now Wicked supplanting Ifup (I never used NetworkManager longer than was necessary to eradicate it), it's hard to keep up with what hasn't recently or not quite as recently changed from a long prior tradition. Meanwhile, as long as it keeps working, I'll apparently just need to ensure net.ifnames=0 is included in all my post-13.1 Grub stanzas, and included for all installations.
Udev rules are ignored by initramfs. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 2014-08-20 12:35, Stefan Seyfried wrote:
Am 19.08.2014 um 08:08 schrieb Felix Miata:
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
Interface naming [...] is all done by udev. And you should know that after all these years.
https://bugzilla.novell.com/show_bug.cgi?id=868375
Udev rules are ignored by initramfs.
No, they are not (completely) ignored. https://plus.google.com/109464953059773945656/posts/PfCz13VjtWv -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (7)
-
Andrei Borzenkov -
Cristian Rodríguez -
Felix Miata -
Jan Engelhardt -
Robert Schweikert -
Sid Boyce -
Stefan Seyfried