Web lists-archives.com

Re: Naming of network devices - how to improve it in buster

On Fri, 2017-07-14 at 11:20 -0300, Henrique de Moraes Holschuh wrote:
> MOST PCI/PCIe NICs indeed use "ethX", etc.  But the naming scheme
> really is device driver-specific, and the "default" name used by a
> driver is considered part of the kernel stable ABI, and cannot be
> changed on the kernel side unless it is done opt-in at kernel config
> time (kconfig) or at boot time (kernel command line, device tree,
> etc).

Which is a PITA.  Even though udev does it's best to work around it,
the advice "don't clash with the kernel's naming scheme" is excellent
advice.  It's just a shame the kernel doesn't have a well defined
naming scheme, so it's impossible to follow in the general case.

The funny thing is the despite all the heat generated by this
persistent network interface discussion, it's not a huge problem
because the tools exists to work around it.  You just have to know
where to look.

What I do get regularly bitten by is other devices changing their
names, in particular tty's coming back as different names when someone
reconnects a USB cable.  If there is a general, scriptable way around
that problem that means I don't have to say "reboot the box" I haven't
found it.

Attachment: signature.asc
Description: This is a digitally signed message part