Fear not, systemd lovers, for there is piss enough in my balls to widdle all over sysvinit as well. Runlevels are dumb, and an init system shouldn’t try to manage services. Its job is to get the system into a state where the service manager can do its own job, monitoring services.
Hot take: Systemd hasn’t “proved itself”, you just gaslit yourself into thinking it’s better.
back in the day it made sense to relaunch login when wait() indicated that it died. when rc was simple, storing the current runlevel and running the in/out scripts to cross run levels made some sense too since 1 can exit on shutdown. systemd exists because we put off libc level service support.
Which is funny, because podman used varlink, RH canned development of varlink and they replaced it with REST. Now systemd wanna follow suit instead
rpi 5 pros: it's fun to have as mall linux box to play with rpi 5 cons: systemd exist
systemd is truly a cursed beast
I'm still not sure if I've successfully written a systemd timer and I've written three
achievement unlocked: after days of googling and experimentation, i can now setup full disk encryption + auto TPM unlock on a systemd-based linux. something windows could do without even asking. 🤷♂️
if you've been hit by a very fucking weird regression with hardware acceleration with chromium, it looks like adding i915 to your modules in mkinitcpio completely solves this problem for reasons i cannot understand maybe systemd-boot doesn't load it in the same way that udev/busybox does but lol