I wish systemd would just die a fiery death. Every two years I replace my environment - by design, to force growth. I've been doing this on Linux since 1993.

I wish systemd would just die a fiery death. Every two years I replace my environment - by design, to force growth. I've been doing this on Linux since 1993. In my most recent go-around, I hunted for a Unix distribution that could meet my needs, and played with: Void, Solus, Manjaro, Fedora, Tumbleweed, TridentBSD, and GhostBSD. Heck were there docker support on *BSD I'd be back there happily for the first time since 2001. SystemD needs to die because it violates Unix principles, not because of it's new key combinations. Unix is built on the notion that everything is a file, and that purpose built binaries make sense. SystemD breaks the latter - meaning it's now significantly more work to do the same things when it comes to log investigation, service analysis, and related events. Perhaps the worst part is the extension of a subsystem for service initialization to everything other than that. The folks at suckless (https://suckless.org/sucks/systemd/ https://suckless.org/sucks/systemd/) did the argument significantly more justice than I ever could.