"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: There's another "movement" to boycott systemd... (Score: 2, Interesting)

by Anonymous Coward on 2014-09-07 19:44 (#2S4N)

However, I *do* like installers. Slack has a lot of nice points, and I even installed it once. But I moved back to Debian fairly quickly...and Debian has bought into systemd. Gentoo also doesn't have an installer, though it at least has a package manager. BSD doesn't support even reading ext4 systems on large disks, so that's out of consideration.

But I'm heard exactly ZERO reasons why *I* should like systemd.
Post Comment
Subject
Comment
Captcha
Of the numbers seventy five, 83, 16, 35, 89 or fifty six, which is the largest?