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: 1) by chris.alex.thomas on Sunday September 21 2014, @10:36AM

    by chris.alex.thomas (2331) on Sunday September 21 2014, @10:36AM (#96236)

    it took all of ten seconds to open google, type "systemd debugging" and found this

    https://activedoc.opensuse.org/book/opensuse-reference/chapter-8-the-systemd-daemon [opensuse.org]

    I suppose you could have done the same and know how to debug it if you have problems.

    and are you still talking about PID1 ??? barely any part of systemd runs as pid1, it's all branched off and the benefits far outweigh the problems, I've also had a problem with my system which was practically impossible to fix and it was using the old init.....systemd is faster and better designed than the old sysvinit.....

  • (Score: 0) by Anonymous Coward on Sunday September 21 2014, @01:08PM

    by Anonymous Coward on Sunday September 21 2014, @01:08PM (#96302)

    Did you actually read what you linked to? Have you ever done any actual shell script or software debugging on Linux?

    Debugging init scripts sounds FAR easier than doing that sort of systemd debugging that's described. Binary log files? Jesus Christ, that has just made debugging 8x harder, even if there are tools to work with those binary log files. And what's to say that these complex tools are even working if the system is really screwed up? Nothing! Yet we can usually rely on sh and ed to be working, since they follow the UNIX philosophy by doing one thing, and doing it really damn well.

    • (Score: 0) by Anonymous Coward on Sunday September 21 2014, @03:03PM

      by Anonymous Coward on Sunday September 21 2014, @03:03PM (#96343)

      I know very little about systemd, but I have been a unix dev for 20+ years now and one thing I am qualified to say is that binary log files are a terrible, terrible thing. They should only ever be used when the alternative is no log files. They are so unfriendly to developers, and it has a way of biting you in the ass when you least expect it. Being able to manually run them through a translator is only good enough for the most low-impact bugs.

  • (Score: 2) by sjames on Sunday September 21 2014, @04:01PM

    by sjames (2882) on Sunday September 21 2014, @04:01PM (#96354) Journal

    So, when I want it to go step by step and stop in-between each step,.....

    How about if I resort to init=/bin/bash and then wish to start the services manually? It seems systemd can't do it's thing without that chunk sitting on PID1 (where my shell is)

    I'll be sure to use all those pretty tools as soon as the system comes up far enough that I can. I gues if the problem prevents getting to that state your solution is to reinstall Window^w Linux?