SoylentNews is people
SoylentNews
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.
(Score: 2) by sjames on Sunday September 21 2014, @04:01PM
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?