https://bugzilla.novell.com/show_bug.cgi?id=843677 https://bugzilla.novell.com/show_bug.cgi?id=843677#c Robert Milasan changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|NEW |ASSIGNED AssignedTo|bnc-team-screening@forge.pr |rmilasan@suse.com |ovo.novell.com | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=843677 https://bugzilla.novell.com/show_bug.cgi?id=843677#c3 --- Comment #3 from Robert Milasan 2013-10-03 06:31:40 UTC --- Can you also run: udevadm test /sys/class/net/eth0 udevadm test /sys/class/net/rename3 and attach the output to the bug? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=843677 https://bugzilla.novell.com/show_bug.cgi?id=843677#c5 --- Comment #5 from Bernhard Wiedemann 2013-10-04 11:49:34 CEST --- (In reply to comment #2)

Actually is ln -sf /dev/null /usr/lib/udev/rules.d/80-net-name-slot.rules not what you wrote.

then upstream docs are wrong?

What does it mean: 'we need a way to easily get predictable network device names like "eth0"' ?

I meant, if we prepare an image for a liveCD, it can include a /etc/sysconfig/network/ entry for eth0 with DHCP, but it can not include configs for all possible device names, so we need a predictable network device name like eth0 there. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=843677 https://bugzilla.novell.com/show_bug.cgi?id=843677#c7 --- Comment #7 from Robert Milasan 2013-10-04 09:55:15 UTC --- (In reply to comment #5)

then upstream docs are wrong?

Yes, seems like that.

I meant, if we prepare an image for a liveCD, it can include a /etc/sysconfig/network/ entry for eth0 with DHCP, but it can not include configs for all possible device names, so we need a predictable network device name like eth0 there.

I know we would need an alternative, but this is not a udev issue, but a yast issue, something needs to generate them. You still didn't gave me all the info which I requested. Also net.ifnames=0 works perfectly in my tests. Whats with the rest of the network devices available ? /sbin/ifconfig -a -- 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.