"Boycott Systemd" movement takes shape

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: Last time I spoke to myself... (Score: 2, Interesting)

by scotch@pipedot.org on 2014-09-08 08:26 (#2S4V)

I started to use Linux long time ago (at that time I was a hobbyist and PhD student in engineering but now I'm a sysadmin by trade) because I wanted to understand every bit of my system and to be able to follow every execution path on it. Today it's becoming increasly difficult even impossible. I used redhat 4 then mandrake then debian (potato). It was fun, it ported values I do agree with, it fitted my needs. I started with one box in my attic up to 22 boxes in my garage before moving to the datacenter. Now I'm unhappy with the direction debian is heading. I loved squeeze but wheezy is not my cup of tea. I tried gentoo for awhile but on the production servers I manage I don't want to compile anything (not even installing the compiler...). I'm now trying alpine (discovered from the weekly distro post ;) ).
The major problem I see with systemd is that rebooting for some application upgrade is not an option but on kernel change (if the "new" fix is for an problem I encounter, not just for the sake of it). Also the involved "new" complexity is another major pain. I liked stable system and by stable I don't just mean "with no random crashes" but with no changes for the sake of change.
I suppose I will need to take (loose?) a lot of time trying to find another distro (even not linux) fiting my needs while still being fun to administer and being understandable at low level...
They are improvements in the landscape but also a lot of regressions :(
Post Comment
What is twenty six thousand six hundred and thirty four as digits?