The "removing systemd" experiment
Conclusion and Other Resources
- Replacing the systemd startup from a systemd-controlled distribution by SysVinit or something else is comparably easy if dependencies are kept in place.
- Removing systemd-introduced dependencies causes side effects on session management that need to be resolved with some manual configuration work.
- The effort needed for maintaining a non-systemd-controlled distribution may increase with systemd's development progress (i.e., "it will never be finished").
Several HOWTOs are available for removing systemd partially or completely [3]-[5], recompiling packages without systemd dependencies, or simply choosing a GNU/Linux distro alternative that uses a different system to manage software [6]. The "pinning" of packages, especially, seems to be a good idea to prevent semiautomatic upgrades from "updating" a new systemd version over the no-systemd package and thereby causing conflicts.
Infos
- Systemd: https://www.freedesktop.org/wiki/Software/systemd/
- Actually,
systemd-logindwill cause more trouble thansystemditself later. - Removing systemd from Debian: http://lkcl.net/reports/removing_systemd_from_debian/
- Removing systemd from Ubuntu 16.04 and preventing its usage: https://askubuntu.com/questions/779640/how-to-remove-systemd-from-ubuntu-16-04-and-prevent-its-usage
- Removing systemd from a Debian jessie/sid installation: http://without-systemd.org/wiki/index.php/How_to_remove_systemd_from_a_Debian_jessie/sid_installation
- Systemd and alternatives: http://without-systemd.org
« Previous 1 2 3
Buy this article as PDF
Express-Checkout as PDF
Price $2.95
(incl. VAT)
(incl. VAT)
Buy Linux Magazine
TABLET & SMARTPHONE APPS
US / Canada
UK / Australia