Slash Boxes

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 18 submissions in the queue.
posted by azrael on Sunday September 21 2014, @07:37AM   Printer-friendly
from the use-as-much-as-you-want dept.

A developer affiliated with 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.

This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Sunday September 21 2014, @11:35AM

    by Anonymous Coward on Sunday September 21 2014, @11:35AM (#96256)

    it runs everything as pid 1?? doesn't, if you at least read for 5 minutes, googled for 5 minutes, you'd find it DOESNT do that....

    And if you googled for 2 minutes, you'd find this is not the complaint. Of course you already know this, strawman withstanding.

    you don't want your entire system to be dependant on a single piece of software? as linus said the other day, better stop using the kernel then....

    Apples to oranges. The way systemd is 'evolving' it won't be long before it contains it's own kernel.

    are any of the people loudly complaining even affected by this? if all you do is say write software in GTK or Qt, why would you ever care about the init process, it's not your business, as long as it works and it does the job, why do you want to get involved and argue?

    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

    by fritsd (4586) on Sunday September 21 2014, @06:10PM (#96386) Journal

    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

    by HiThere (866) Subscriber Badge on Sunday September 21 2014, @07:42PM (#96412) Journal

    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

    by hendrikboom (1125) on Monday September 22 2014, @12:45AM (#96519) Homepage Journal

    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

      by FatPhil (863) <reversethis-{if.fdsa} {ta} {tnelyos-cp}> on Monday September 22 2014, @06:34AM (#96633) Homepage
      There've been efforts to push stuff out of the kernel. Migration against statically linked board files towards DT. Before that, migration against both static /dev trees and kernel-controlled dynamic dev trees towards a user-space daemon-controlled dynamic /dev tree. Userspace helpers popping up in all kinds of places, such as in teh pluggable security modules. OK, there's been migration in the other direction too, but that's generally made sense. KMS was something that belonged in the kernel, and it's absurd that it wasn't there for so long.

      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