"Boycott Systemd" movement takes shape

by
in linux on (#2S4F)
story imageSome people have had enough, and they've organized a boycott at "http://boycottsystemd.org" to organize efforts. From the top: "Disclaimer: We are not sysvinit purists by any means. We do recognize the need for a new init system in the 21st century, but systemd is not it." OK, that's enough to keep me reading. They outline twelve well-thought-out reasons systemd is dangerous, and a set of ways you can get involved, including refusing to use systemd distros, moving to slackware, crux, gentoo, BSD, and more. Here's just one of them:
systemd clusters itself into PID 1. Due to it controlling lots of different components, this means that there are tons of scenarios in which it can crash and bring down the whole system. But in addition, this means that plenty of non-kernel system upgrades will now require a reboot. Enjoy your new Windows 9 Linux system! In fairness, systemd does provide a mechanism to reserialize and reexecute systemctl in real time. If this fails, of course, the system goes down. There are several ways that this can occur9. This happens to be another example of SPOF.
Interesting times. When's the last time you heard someone advocate moving immediately to Slackware or Gentoo?

Re: Contradiction (Score: 1)

by zafiro17@pipedot.org on 2014-09-08 19:06 (#2S5S)

I modded you up because that's a great link - very informative. I notice though that the argument consists of, for the moment, people talking past each other. That is, I don't see much in Debian's position statement that refutes what the anti-systemd crowd is putting forth as their argument.

Can't wait to see how this plays out. I confess I am for the most part more swayed by the anti-systemd crowd's position, but I like transparency and simplicity in a system, and systemd decreases both.
Post Comment
Subject
Comment
Captcha
What number is 5th in the series nineteen, four, thirty two, twenty eight and eleven?