A friend on Diaspora has been asking a lot of questions about systemd lately, and the more he learns and posts about it, the scarier it seems. Not so much for the present, but for the control it takes over everything in the OS (and choice is a big deal for most Linux users, even for simple technophobic “ordinary users” like me). It’s a “supervisor” for all running processes on a Linux system which has it built in (Debian, Red Hat, Fedora, CentOS, Ubuntu and all it’s children and grandchildren like Linux Mint, Linux Lite, ElementaryOS, Bodhi, and dozens of others). He had asked why systemd requires it’s own password, which I didn’t know about. And like the nice helpful boy I want to be, I searched for the answer to share with him. Here’s a a little of the conversation:
I’m not trying to start a new debate, since I don’t know enough about it to contribute anything except that there are still some great systemd-free Linux OSes around, from AntiX and Devuan (Debian-based) to PCLinuxOS and of course, Slackware (the oldest active Linux distro in existence) and it’s derivatives like Vector Linux and SalixOS. That’s all I can contribute to the debate, but here’s why I’m a little spooked by all this systemd stuff:
Politically arch-conservative, my “default setting” is to completely mistrust the government and big intrusive corporations like Microsoft and Google anyway, but from the conversation above (and about 70 more comments in that thread), it seems almost like systemd is trying to take over Linux! It’s initialized on boot-up even before the kernel for goodnessakes, and has “agents” to coordinate and keep a record of every process. Okay, it’s supposed to make everything better somehow I guess, but keeping a record of everything? This really does sound like the start of a “slippery slope” that is supposed to be the new standard for the most popular Linux desktop and server operating systems.
That’s why I’m spooked.
Now for the hopeful part:
If I jump back to Salix to avoid systemd, I would really miss the cool tools I have with my modified Linux Lite – particularly the tools from this wonderful site maintained by a quiet coder who has adapted stuff from other great Linux distros for Linux Lite and Linux Mint. So just for giggles, I searched for a Slackbuild of MintStick, the supercool USB utility that not only writes iso images to a USB thumbdrive, but also lets you format USB sticks with two mouse clicks. And guess what?! Sure enough, there’s a Slackbuild for that! Updates are never an issue in Salix (fully compatible with Slackware). It’s stability is legendary and “broken after updating” is so rare I’ve never even read any such thread in the Salix forums. Linux Lite is awesome for now – modified with the unlockforus stuff – but it’s future is uncertain.
Perhaps I’ll revisit PCLinuxOS again, too. It’s been probably 2 years or more since I played around with it. But Salix was always awesome, even without any Gnome stuff in it at all (there are plenty of places to find “Gnome for Slack” packages and scripts anyway). I’m not a big fan of Gnome, since it seems they really didn’t listen to the community at all when they came up with Gnome 3 and ended up losing a lot of users to Mint’s fork of Gnome called Cinnamon, and to other desktops like Xfce, LXDE, etc.
Linux is about freedom. Systemd seems a threat to that freedom. But thankfully, it’s easily avoided – for now.
EDIT: I just finished deleting a few paranoid posts about systemd. As it turns out, most of the issues I uncovered were two or three years old (before systemd showed up in Ubuntu-LTS-based distros) and have long since been patched. And now that it is in such widespread use, there are literally thousands of freedom-loving developers, users, testers, and coders to keep an eye on it. Fear of systemd is not going to rob me of an awesome, simple computer experience.