Bug#881771: release-notes: No mention of "predictable network interface names" in Debian 10
Karl O. Pinc wrote:
> A) Added text in "what's new" section explaining the (sorta-new)
> interface naming scheme and why it's good. Mention there
I hope you're aware that the last release-notes announced in
https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#new-interface-names
that "predictable"-style nicnames were already the default for
Stretch unless overridden in /etc/udev/rules.d/. And they
referenced the udev README that says this mechanism won't be
supported in Buster - the justifications struck me as weak, but
given a full release cycle's advance warning I wasn't going to
object.
> C) Actual upgrade instructions. This is in-progress.
>
> There are really 2 paths for manual migration of
> interface names: one for when you have console/physical
> access and another when you don't. In the first case,
> you can try the new names, see what name you get, and
> migrate /etc/. Without console access you need to
> calculate the new interface name, migrate, and hope
> you got the right name after reboot. To calculate
> the right interface name you need additional background
> information. I've whacked up a teeny script, with
> no dependencies, to compute the common case. But it
> does require the pciid as input, and I suggest installing
> pciutils to get lspci to find pciids.
Whether I'm accessing it physically or via ssh, can't I use something
like:
udevadm test /sys/class/net/$ETHX 2>/dev/null | grep NET
or
udevadm test-builtin net_id /sys/class/net/$ETHX 2>/dev/null
...? That worked for me even on Jessie machine.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
Reply to: