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
I think I’ve done it. I now have my own home IaaS.
I went for the OpenStack approach, Packstack with RDO on Scientific Linux. In the future I want to replace SL6 with Gentoo on the bare metal, and install the OpenStack packages from portage, but I’ll wait for the work from a Gentoo dev who knows what he’s doing.
This also means that the running hypervisor is KVM, not the Xen that I would rather be using. Technically, there isn’t much difference to them, but Xen is the hypervisor used by AWS, PV images can be booted without fiddling with partitioning and bootloaders. That’s so ’90s.
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.
Hi future me,
IPv6 is probably ubiquitous when you’re reading this. But I’m speaking too soon, then here’s some quick tips about setting up your own subnet.
I’ll make some assumptions, the network (specifically the router) already has a /64 subnet and prefix. For the sake of example, lets pretend these are:
2001:DB8:1234:5678::/64 - the subnet 2001:DB8:1234:5678::1 - the router inside that subnet
Hi future me,
Sometimes you’re going to find yourself needing to boot some very archaic CDs. But CD drives might not exist in the future, so you’re stuck with USB to shim the ISO. (I think that first sentence should get all of the Google hits, but lets include some more buzzwords such as LiveCD, LiveUSB, syslinux etc.)
Hi future me, just a reminder that you forgot this last time. But booting a mactel doesn’t need special “bless”ing. Just remember to install grub2 properly.
grub2-install --target=x86_64-efi --efi-directory=/boot --removable --modules=part_gpt
Also, grub2 doesn’t seem to come with vbe.mod anymore. So on Calculate Linux, edit /etc/default/grub and change GRUB_VIDEO_BACKEND=”vbe” to something sensible. Perhaps “all_video”. Then re-run grub2-mkconfig.