Wookey <woo...@wookware.org> writes:
> Which entry in which release notes will warn that this time
> (presumably - was this an upgrade to unstable K.C. or to bookworm, or
> something else?) the (pretty old now) eth0 -> 'annoying, unmemorable,
> but ordered and unique', renaming will/might actually break your
> config?
There probably hasn't been a warning since buster, when the release
notes [1] warned:
4.1.6. Verify network interface name support
Systems upgraded from older releases that still use network
interfaces with names like eth0 or wlan0 are at risk of losing
networking once they switch to buster; see Section 5.1.6,
“Migrating from legacy network interface names” for migration
instructions.
Maybe all release notes after this should have warned about using
systemd unpredictable interface names on headless systems? Particularily
on systems with a single network interface, where such breakage is
completely unnecessary and "eth0" is guaranteed to be stable from kernel
to kernel.
We should probably also advise users of headless systems with multiple
interfaces that they need to manually configure names for their
interfaces. Personally I prefer more descriptive names like "uplink",
"backend" etc. Avoids the systemd breakage and makes network config
easier to read/debug.
Bjørn
[1] - https://www.debian.org/releases/buster/amd64/release-notes.en.txt
