Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 16 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 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: 0) by Anonymous Coward on Monday September 22 2014, @09:13AM

    by Anonymous Coward on Monday September 22 2014, @09:13AM (#96666)

    Systemd is a huge binary blob, where as both sysv-based and bsd-based init systems are a simple binary (on the scale of a couple of bugs being found per decade) that hand everything important over to shell scripts.

    A unix admin is more or less a shell script expert, often with minimal C skills.

    Debugging a shell script is on level with turning off the coffee machine for these guys, where as C code with any level of complexity would likely result in sending mails to the developers and spending a lot of time waiting for replies.