Re: [systemd-devel] network interface names flipping

2015-10-16 Thread Tomasz Torcz
On Fri, Oct 16, 2015 at 04:44:34PM +0200, Olaf Hering wrote:
> Since the introducion of the (un)predictable network interface names the
> name of the single onboard interface on my Shuttle changes if I boot my
> own .config or the kernel.rpm provided by openSUSE. I just threw up
> hands and continue to boot with netnames=0 (or whatever).
> 
> 
> So, with my own kernel "eth0" becomes "enp2s0". And as I noticed just
> now, with kernel.rpm its always named "ens1".
> 
> What is udev doing wrong?
> See http://pastebin.com/raw.php?i=Y5NJWJGF for some data.

  udev takes info from firmware.  Does openSUSE kernel package
carry any patches fixing/changing what firmware reports?

-- 
Tomasz   .. oo o.   oo o. .o   .o o. o. oo o.   ..
Torcz.. .o .o   .o .o oo   oo .o .. .. oo   oo
o.o.o.   .o .. o.   o. o. o.   o. o. oo .. ..   o.

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] network interface names flipping

2015-10-16 Thread Kay Sievers
On Fri, Oct 16, 2015 at 4:44 PM, Olaf Hering  wrote:
> Since the introducion of the (un)predictable network interface names the
> name of the single onboard interface on my Shuttle changes if I boot my
> own .config or the kernel.rpm provided by openSUSE. I just threw up
> hands and continue to boot with netnames=0 (or whatever).
>
> Now that same thing starts to happen on my Probook, and that makes me
> wonder if the whole code should just be dropped from udev because it
> obviously fails to work. Unless of course the goal is "UNpredictable"
>
> So, with my own kernel "eth0" becomes "enp2s0". And as I noticed just
> now, with kernel.rpm its always named "ens1".
>
> What is udev doing wrong?
> See http://pastebin.com/raw.php?i=Y5NJWJGF for some data.

Your own kernel might not support PCI hotplug? The slot names might
not be available if the support for them is missing.

Btw, predictable means it will not change between reboots, that names
will not depend on enumeration order within the same setup. It does
not mean or promise, that added kernel/driver/firmware features will
not result in different names. That is expected behavior.

Kay
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


[systemd-devel] network interface names flipping

2015-10-16 Thread Olaf Hering
Since the introducion of the (un)predictable network interface names the
name of the single onboard interface on my Shuttle changes if I boot my
own .config or the kernel.rpm provided by openSUSE. I just threw up
hands and continue to boot with netnames=0 (or whatever).


Now that same thing starts to happen on my Probook, and that makes me
wonder if the whole code should just be dropped from udev because it
obviously fails to work. Unless of course the goal is "UNpredictable"

So, with my own kernel "eth0" becomes "enp2s0". And as I noticed just
now, with kernel.rpm its always named "ens1".

What is udev doing wrong?
See http://pastebin.com/raw.php?i=Y5NJWJGF for some data.


Olaf
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel