|FROM ||Ruben Safir
|SUBJECT ||Subject: [NYLXS - HANGOUT] purging systemd
Prevent systemd installation
Jump to: navigation
Several distributions such as Debian, Arch Linux,
etc. have switched from
systvinit to systemd .
However, some people prefer to keep their initialization system the ways
it was, or use something they feel is superior to systemd.
This page shows you some of the ways to prevent systemd being installed
on your operating system during upgrades or other package installs.
* 1 For Debian based systems
o 1.1 More ways to prevent systemd on Debian
* 2 For Gentoo/Funtoo based systems using Portage
* 3 For ArchLinux based systems
* 4 For Fedora
* 5 For Slackware
* 6 For Dragora
* 7 For Crux
* 8 For Exherbo
* 9 LSD linux (Less SystemD linux)
* 10 VoidLinux
* 11 Devuan
* 12 VoidBang
* 13 additionally
o 13.1 bedrock
o 13.2 further tips and advice
+ 13.2.1 polkit and consolekit
* 14 alternatives
o 14.1 not quite systemd
* 15 External links
For Debian based systems
In your /etc/apt/preferences, add:
Pin: origin ""
More ways to prevent systemd on Debian
This method is perhaps overkill: 
There are more suggested ways to be fished out of: 
Thanks to KittenGNU for this tip: "The MirOS repo has some virtual
packages to prevent lennartware to install" 
see devuan, a systemdless debian fork, scroll down.
For Gentoo/Funtoo based systems using Portage
Simply include the "-systemd" useflag in your /etc/portage/make.conf, like:
(...along with whatever other useflags you have of course)
another technique seen in some users' make.conf includes use of
which will prevent the package manager for making directories and files
For ArchLinux based systems
Add in your /etc/pacman.conf:
(as advised in the pacman page of archwiki)
arch forum has a section dedicated to this topic.
Solution not yet found ~ please help contribute if you know how ~ The
best offering found so far was a thread full of people saying to use
another distro. It seems from this that you are not free to pick your
own init system in fedora. 
~Please share if
u have a solution.
Slackware currently has shown no signs of addopting systemd as default
init. (So you dont need to do anything)
Dragora currently has shown no signs of replacing runit with systemd as
default init. (So you dont need to do anything)
Crux currently has shown no signs of replacing their bsd-style init with
systemd as default init. (So you dont need to do anything)
In /etc/paludis/options.conf, add
Exherbo may promote systemd foremost in the installation guide, but
makes no effort to restrict you to it, and you are free to choose your
own alternative upon install.