Forks · systemd/systemd
github.com
The systemd System and Service Manager . Contribute to systemd/systemd development by creating an account on GitHub.

The latest changes implemented in the Systemd repo, related to or prompted by age-verification laws, have made many people unhappy (I suppose links about this aren’t necessary). This has led to a surge in Systemd forks during the last days (“surge” because there have always been plenty of forks). Here are some forks that explicitly mention those changes as their reason for forking (rough time ordering taken from the fork page):

Hopefully the energy of this reaction won’t be scattered among too many alternatives, although some amount of scattering is always good.

  • z3rOR0ne@lemmy.ml
    232·
    20 hours ago

    Fair Warning: Long anti-systemd rant ahead.

    Here’s a list of some fine, totally usable, and well maintained Linux distros that don’t use systemd:

    • Artix Linux (offers 4 different supported init systems)
    • Gentoo Linux (supports systemd/openrc, with documentation provided on how to manually support others)
    • Void Linux (uses runit)
    • Alpine Linux (uses openrc, most docker containers use this as their base)
    • Devuan (offers 5 different supported init systems)
    • Antix (offers 5 different supported init systems)
    • MX Linux (offers systemd/sysv init)

    Honestly, I was on Artix for 8 years and am on Gentoo/openrc now (been about 6 months). I never really got the systemd hype. I don’t even bother with it on my servers where I just run Alpine Linux. It’s just…not really needed unless the dev of a particular DE or app doesn’t know how to use basic GNU tools and/or doesn’t know they don’t need init for such and such feature.

    Yeah yeah, systemd isn’t just an init system. People make that argument all the time, but honestly, that’s actually an argument against using it.

    Systemd is poorly designed if the init component can’t be separated out from it’s various other utilities. If I could use systemd just as init, maybe it wouldn’t be…y’know, crap. But no, it has to handle DNS, cron, logging, login managment, etc.

    Again, no problem if the systemd devs wanted to make it a suite of optional tools, but init systems are and always will be best if their codebases are as tiny as possible while still being usable and secure. Init’s only job is to fork other processes that the user specifies, that’s it.

    Honestly if some software uses systemd, I’m not likely to use it unless someone’s paying me to. Heck, at work I use all sorts of shitty tools that frustrate me to no end in exchange for money.

    But if I do happen to use software that requires systemd, on a system that I own, I’m likely to just go into the code, rip out the parts that utilize it, rewrite it, and recompile the binary because fuck that. Yes, I’ve done this. Most of the time, it’s not that hard. But I can count on one hand the amount of times this has been necessary, because the maintainers of these non-systemd distros are able to write basic scripts that hook into the various init systems and you just use them.

    And if some major DE like GNOME or KDE relies on systemd, I’d just say, fuck’em. There’s plenty of DE’s that don’t and a multitude of WM’s that never will, and good, they shouldn’t.

    Rant over.