Switching to a non-systemd system when you've gotten used to the convenience of .service and .timer files is really no fun at all. I'm sure there is a lot of stupid shit in the giant bundle that is systemd, but service files make administrating systems *way* more understandable and accessible.
@rixx My worst xp with SysV is still that you need to put all the services in correct order in rc.conf (iirc) and you cant specify dependencies (or do a dep check for cyclic deps). In this point systemd is way better - imho.
@rixx That. And the possibility to override *parts* of a file by dropping snippets into .service.d folders.
@rixx agreed. I'm (by far) not a full blown Linux admin, but the unit files and timers are nicer than the ugly shell scripts from the past. So far only hit minor nuisances (like reverse-resolving the default gateway IP to "_gateway" and not being able to turn that off), but in general a bunch of stuff makes more sense to me.
@rixx So you are actually switching to OpenBSD? Nice. May I ask what specifically drove you to that decision? I'm always interested in other people's motivation to move to the BSDs.
@raichoo Not switching, just test driving. The lack of systemd style services may well be the reason against a full switch - I use them heavily for running pretalx and related projects. My reason for testing it in the first place is mostly curiosity and the great community.
@rixx Ah I see :) Thanks for filling me in :)
@rixx runit had dependencies and shit way before systemd came around.
@rixx I second this. I've recently tried to run a system with OpenRC, and while it is way better than the nightmare e.g. Debian has … well, _is_ still partly using, I've stumbled upon problems I didn't even remember they'd been solved with systemd.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!