https://bugzilla.novell.com/show_bug.cgi?id=849749 https://bugzilla.novell.com/show_bug.cgi?id=849749#c11 --- Comment #11 from Ralf Friedl <Ralf.Friedl@online.de> 2014-03-11 11:44:40 UTC --- (In reply to comment #10)
This issue seems to be due to hardware, but also because of the implementation currently available in systemd/udev.
Basically, that upstream said, is that the BIOS or hardware in general does this and it shouldn't (cheap hardware, broken firmware, broken BIOS, etc). The board is from Gigabyte, so not exactly a cheap one.
Is there a specification that says that the assigned numbers have to be the same across reboots? If not, then it is not cheap/broken hardware, but a flawed assumption in the software.
I, honestly, not sure what direction to take here Can you tell me a single advantage of the new system, compared to the previous state of opensuse? The previous state was not to let the kernel assign random numbers, but to make once assigned interface names permanent. Exactly what this change promised to bring, and exactly what it took away. And before, I had the predictable name eth0 for the common case, a machine with only one network interface, instead of enp3s0 or whatever. Even if this name was persistent, it would still be worse than before.
There is a workaround for this issue, meaning manually create the persistent rule, but some people may not like the idea of having to do some extra work.
Great, extra work for things that used to work automatically. If you want to leave it that way, at least make the input field for the interface name in yast (text version) longer (yast lan -> edit -> hardware -> udev rules -> change -> Device name). The field has only 5 characters, and first and last are used as indicators that the content is longer. It looks like this: "-p0s-" -- 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.