"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?

I cannot say that I understand the problem (Score: 2, Interesting)

by tanuki64@pipedot.org on 2014-10-04 16:52 (#2T36)

I am software developer. I develop mostly under Linux. I usually compile my own development tools. Compiler, IDE, non-standard libs. This is not always necessary, sometimes even overkill, but at least this way I know how the stuff is compiled and what the dependencies are. And I rarely get nasty surprises when I do an update/upgrade. So my work stuff is somewhat insulated from the rest of the Linux. Apart from developing stuff I do almost everything with Linux (Debian). I surf, watch movies, print. Linux is my main system. And it works. No problems at all. So I don't really care what kind of init system is used. Maybe I would think different, if I develop for Linux itself. Maybe systemd has problems, which really bite developers, who have to work with it directly or indirectly. However, when I see the noise because of systemd... are there really that many developers, which work on that level? I have the feeling something might be a bit blown out of proportion.
Post Comment
Subject
Comment
Captcha
Which digit is 6th in the number 3375135?