In my quick review of systemd, I left a few points hanging for further elaboration.
I mentioned that there are no official stage3 tarballs with systemd. Without them, the only way to get a systemd system is to upgrade via the guide.
As I get used to it, I’m going to need a way to install systemd repeatedly and consistently. I have therefore created my own stage3 tarball.
It’s been nagging me for a while. I knew that it would happen at some point. I read the blogs, the reviews, the flames. The future of PID1 is here.
I’ve been putting this off for a while, udev-200 was the first visible change. I practiced the upgrade a few times, so I was ready when it stabilised. Replace all instances of eth0 with enpXsY. It seemed harmless enough. For my generic images, adding dhcpcd to the default runlevel, and not creating the net.* specific scripts tends to do well. Hostnames (dhcp/dns coupling) are a bit erratic but some tweaks to the runlevel order fixes those.
This is something a bit more invasive. I can’t upgrade this easily. Continue reading
These past few weeks, there have been some pretty disturbing disruptions for Linux users on rolling release distros.The biggest upset in recent times I’ll describe as “The udev-200 issue”, where the symptoms of an unsupervised update/reboot cycle will present you with a) a system that won’t boot, b) a system without network or c) both.