SoylentNews is people
SoylentNews
A developer affiliated with boycottsystemd.org has announced and released a fork of systemd, sardonically named uselessd.
The gist of it:
uselessd (the useless daemon, or the daemon that uses less... depending on your viewpoint) is a project which aims to reduce systemd to a base initd, process supervisor and transactional dependency system, while minimizing intrusiveness and isolationism. Basically, it’s systemd with the superfluous stuff cut out, a (relatively) coherent idea of what it wants to be, support for non-glibc platforms and an approach that aims to minimize complicated design.
uselessd is still in its early stages and it is not recommended for regular use or system integration, but nonetheless, below is what we have thus far.
They then go on to tout being able to compile on libc implementations besides glibc, stripping out unnecessary daemons and unit classes, working without udev or the journal, replacing systemd-fsck with a service file, and early work on a FreeBSD port (though not yet running).
Responses from the wider Linux community are yet to be heard.
(Score: 0) by Anonymous Coward on Sunday September 21 2014, @11:35AM
And if you googled for 2 minutes, you'd find this is not the complaint. Of course you already know this, strawman withstanding.
Apples to oranges. The way systemd is 'evolving' it won't be long before it contains it's own kernel.
I'm a systems administrator, the init process absolutely is my business and essentially I am creating a custom distro whenever I bring up a new system. What is laughable here is that systemd developers continue to tout features as beneficial to administrators like myself, no matter how loudly we tell them otherwise. It's not the systemd developers business to be dictating how we do our jobs whilst ramming their braindead cluster-fuck of an init replacement down our throats.
(Score: 1) by fritsd on Sunday September 21 2014, @06:10PM
As you are a systems administrator, please help us ignoramuses out in this discussion:
It is said that systemd takes over the syslog function (libsystemd-journal0)
In your personal opinion, was there anything wrong with the way rsyslog worked?
Or in other words, have you read anywhere that the systemd people *explained* why a replacement syslog daemon provided by systemd was necessary, or why theirs was better, in any way?
(Score: 2) by HiThere on Sunday September 21 2014, @07:42PM
When you say " It's not the systemd developers business to be dictating how we do our jobs", you may be wrong. We don't know quite what their jobs are, only what they purport to be. Given recent government and corporate actions, this is something one should keep an open mind about pending actual evidence.
Javascript is what you use to allow unknown third parties to run software you have no idea about on your computer.
(Score: 1) by hendrikboom on Monday September 22 2014, @12:45AM
Bad enough for the whole system to depend on one huge piece of software, such as the Linux kernel.
Worse for it to depend on two.
(Score: 2) by FatPhil on Monday September 22 2014, @06:34AM
With systemd, the flow is only in one direction. It is becoming the grey goo.
Great minds discuss ideas; average minds discuss events; small minds discuss people; the smallest discuss themselves