Slash Boxes

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 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, Insightful) by Anonymous Coward on Sunday September 21 2014, @11:59AM

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

    >the benefits far outweigh any problems, that to me is clear as day...

    If so, then why the thing needs to be pushed by hook or by crook? If it *can* outcompete the other projects, then why the propaganda campaign and the Debian farce? And why your declarations, light on facts but high on shrillness?
    If systemd is competitive, then let it compete. Nobody is asking for anything more. Stop the Embrace-and-Extend, and let the so-called "benefits" become visible to the target audience.
    And in meantime, the developers could maybe learn to fix the bugs. Bugreports are *really* meant not for the future historians a hundred years away; a developer fixing his bugs the same year they were reported, can do wonders to his project's stability. Red Hat people should try it sometime. ;)

    Starting Score:    0  points
    Moderation   +2  
       Insightful=2, Total=2
    Extra 'Insightful' Modifier   0  

    Total Score:   2