Component

systemd, systemd-udevd

Is your feature request related to a problem? Please describe

I changed my GPU from Nvidia to AMD. Everything else in the computer stayed the same.

As a result, the ethernet interface name was changed from enp5s0 to enp7s0 on Arch Linux.

This caused a lot of confusion at first as I don't use Networkmanager or any GUI tool to manage the network and it took a while to realize what had happened. DHCP client was configured to work on enp5s0 and it was now failing.

On QubesOS this problem caused the network VM to fail to start because the device identifier of the network controller was changed and the old identifier was used to attach the controller to the network VM. This is not related to systemd but this is the root cause of the problem with systemd too - for some reason changing the GPU changed the device identifiers of other devices.

Describe the solution you'd like

Not sure.

Describe alternatives you've considered

The old style of naming (eth0, eth1 etc) would have prevented the problem in this case but it's understandable why the new scheme was developed.

The systemd version you checked that didn't have the feature you are asking for

255