https://bugzilla.novell.com/show_bug.cgi?id=843665 https://bugzilla.novell.com/show_bug.cgi?id=843665#c15 --- Comment #15 from Olaf Hering <ohering@suse.com> 2013-10-05 00:20:33 CEST --- (In reply to comment #12)
(In reply to comment #10)
(In reply to comment #9)
enp13s0 and enp14s0 are the new names for eth0 and eth1, respectively. There is an issue (bug#820407) with the renaming due to an active interface, but I think that is independent of this.
Is the device symlink really not there? Was it there in 12.3?
On a freshly installed 13.1b1 system:
# l /sys/class/net/enp14s0/device ls: cannot access /sys/class/net/enp14s0/device: No such file or directory
# l /sys/class/net/*/device lrwxrwxrwx 1 root root 0 Oct 4 20:14 /sys/class/net/enp13s0/device -> ../../../0000:0d:00.0/ lrwxrwxrwx 1 root root 0 Oct 4 20:14 /sys/class/net/eth1/device -> ../../../0000:0e:00.0/
I guess bug#820407 is interfering after all - enp14s0 doesn't get properly renamed during startup. Still, shouldn't mkinitrd work with whatever devices the system has? Ah no, I guess mkinitrd takes the information from /etc/sysconfig/network/ which does list ifcfg-enp14s0.
Maybe thats the case. In the end mkinitrd has to translate the entries in /sys/class/net/ to something in /etc/sysconfig/network/ifcfg-*. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.