I am a Linux user, but I don’t really know how most things work, even after years of casual use on my Main, I just started getting into Devuan and wondered then, what exacly does systemd do that most distros have it? What even is init freedom? And why should I care?
Yep I’m aware of it. Seemed like it worked for a bit, then reverted back to the enp* names. And then all the pages I was finding for manually renaming the devices said to put the files under interfaces.d for deb11 but oddly it only seemed to read those link files for a few reboots, then it would revert back to the enp names. Found something about using OriginalName because the name changes were overlapping, that worked for a few boots and then reverted back to the enp names. So then I found something about a Path statement using the full pci device names, and THAT worked for a few boots and then reverted. So now I found out that the link files have moved to the systemd/network folder so I’m waiting to see how long that lasts…
And I realize it sounds like I’m talking about a system I’ve been running for years… I actually just put together this machine last Thursday. I had to start with Debian 9 because I couldn’t get any newer memory stick images to boot (this machine doesn’t have EUFI support), upgraded to deb10 and everything was still working as expected with the grub lines to disable renaming. Upgraded to deb11 and it all went to hell. I’m having some serious thought of trashing the machine and switching to deuvian now even though I really want to support debian.
Servers are cattle. Take it out the back and shoot it then find a less terrible server.
Uh… there’s absolutely nothing wrong with the hardware, it all works exactly as it should. It’s just systemd’s insistence on rearranging things that aren’t broken, and then changing how you fix the problems it created.
Have you considered Devuan a fork of Debian specifically intended to remove systemd.
I have actually. I saw the post for their latest release earlier today and had been seriously considering switching over. This new machine is to replace my existing firewall as the old one has gone through several upgrades since Squeeze, so I’m trying to get something set up to rebuild everything from a clean installation and then I can simply swap out the hardware (and swap it back real quick if something doesn’t work right away).
Tell that to windows sysadmins. Windows would reaaaaally like to be treated like a pet. I feel for them.
Did a system upgrade overwrite your grub config?
No the changes for “net.ifnames=0 biosdevname=0” were still in there. Those worked fine for debian 8, 9, and 10 (with adjustments made in udev rules to rename eth4 and eth5 to wan0 and wan1), but neither option seemed to have any effect after upgrading to deb11. When I went searching for renaming the devices in deb11, the first several articles all stated to create link files in interfaces.d, but after all the trouble I went looking further and finally found one that referenced putting the link files in the systemd folder. I just linked the files so they are available in both locations, and that change has continued working for several further reboots so I’m crossing my fingers.
Ah, they might have killed that option in newer kernels. Vaguely remember something about it being a temporary fix, I guess its time has come.