Per Jessen wrote:
Per Jessen wrote:
I have a test-system with 13.1b1 where the network interface renaming scheme seems a little inconsistent. For instance, on the first boot-up, I had eth1 and enp13s0.
Now, after a few more reboots, I seem to have acquired "70-persistent-net.rules" with two renaming rules for maintaining eth0 and eth1. I simply do not remember creating this myself, but it looks likes yast is doing something to it. I would like to maintain the old naming scheme, so I'm actually happy with this, but something isn't quite right with the new scheme.
I renamed "70-persistent-net.rules" to "70-persistent-net.old" and rebooted. After reboot, I had a new fresh "70-persistent-net.rules". I like this, but I don't want to rely on it if it Is not the intended behavior?
Please ignore this. I forgot I had reverted this system to 12.3. Apologies for the noise. -- Per Jessen, Zürich (16.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org