Stories
Slash Boxes
Comments

SoylentNews is people

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 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.

 
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: 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
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2