On Thu, 5 Jun 2025 13:58:33 +0200 Emanuele Rocca <e...@debian.org> wrote:
A way to address this issue could be, to freeze the naming scheme upon first installation of the system. Say you install a new bookworm system with systemd v252, you pin it to net.naming_scheme=v252.Hi Luca,On 2025-05-21 10:39, Luca Boccassi wrote: > This is expected due to kernel changes. Names can always change if the > kernel changes its internal behaviour, you have to fix them if you > don't want that to happen. This is documented at:> > https://www.freedesktop.org/software/systemd/man/latest/systemd.net-naming-scheme.htmlDoes this mean that all interfaces called enpXs0 on Bookworm will be renamed to ensX when upgrading to Trixie?
Upgrading the system to trixie which has systemd v257, it would stay with the previous naming scheme.
The obvious downside would be, that newly installed systems potentially behave differently then upgraded systems. Another aspect is, that this net.naming_scheme can (currently) only be set via a kernel command line parameter and the integration with grub could be fiddly.
Michael
OpenPGP_signature.asc
Description: OpenPGP digital signature
