[grantla]

> as they deprecated much more invasive things in the past (e.g., cgroupv1) I'd expect them to also drop older versions here, breaking ones naming again

Note that the naming scheme is in control of systemd, not the kernel. Even if it is passed on the kernel commandline.

[tlamponi]

Yeah, I know, I spent more than a week into looking for options to reduce impact for all of our users.

And note that cgroupv1 also still works in the kernel just fine, only the part that systemd controlled was removed from systemd. You can still boot with cgroupv1 support on, e.g., Alpine Linux and OpenRC as init 1. So not sure if that will lessen my concerns about no guarantees for older naming-scheme versions, maintaining triple digits of them sure has its cost too.

And don't understand me wrong, sunsetting cgroupv1 was reasonable, but it was a lot of churn, it at least was a one time thing. The network interface naming situation is periodic churn, guaranteed to bite you every now and then just by using the defaults.

[Scramblejams]

Can you tell me why NamePolicy=keep doesn't do the trick?

Looking myself for options to keep a Debian bare metal server I admin from going deaf and mute the next time I upgrade it... It still uses an /etc/network/interfaces file that configures a bridge for VMs to use, and the bridge_ports parameter requires an interface name which, when I upgraded to Bookworm, changed.

At this rate maybe I'll write a script that runs on boot and fixes up that file with whatever interface it finds, then restarts the network.