Hacker News new | ask | show | jobs
by lovelearning 4284 days ago
Assuming that everything the author says turns out true - such as the "big one" exploit - in say an year from now, does anybody know any active popular open source distro that aims to keep systemd away from servers?
4 comments

Debian has only made systemd the default, and getting sysvinit back is as simple as running `apt-get install sysvinit-core`.

Removing systemd might have consequences for GNOME, but that's not a concern on servers. There is a significant enough anti-systemd contingent in Debian (not to mention Debian also supports kfreebsd, where systemd doesn't run) that I'm confident sysvinit will remain a viable option for servers and non-GNOME desktops on Debian. Even GNOME desktops may work on Debian without systemd thanks to the work being done on systemd-shim.

"...and getting sysvinit back is as simple as running `apt-get install sysvinit-core`"

Well I gather that is the intention but there are a few bugs at present around that and an ongoing issue about upgrade from Wheezy to Jessie changing the init system silently. See Debian-devel for gory details.

Really appreciate that overview. It does seem that even if the author's concerns are true, we still have good alternatives available.
Slackware, CRUX, Funtoo and Gentoo are some distros that follow traditional Unix paradigms and unlikely to adopt systemd.
Patrick has not ruled out using systemd. But if that does happen, I will personally write a tool to drop-in replace all of systemd and return the original sysvinit functionality, and make it work for every distro.
Gentoo still has OpenRC as the „preferred” init system.
Try any of the *BSD OSes.