2 ms·

And this is another fine case demonstrating how very very wrong that criticism is. All in all extremely few systemd subsystems require systemd. Systemd's pid1

And this is another fine case demonstrating how very very wrong that criticism is. All in all extremely few systemd subsystems require systemd. Systemd's pid1 requires only one subsystem, journald, which one can mostly disable/defang if they really dislike it. It's much more like a monorepo than monolith. There's standard practices & libraries between the projects- unit files, ability to ask for machine readible outputs, others. But these cross cutting concerns mostly get compiled in. The actual interdependencies between subsystems are few & far between. Feels like the critics dont really understand what they are trying to criticize.

CameronNemo 5y ago
You say this, but systemd-udevd at one point would sigkill every process on the system if it was not started under systemd (or otherwise in its own cgroup).
- throw0101a 5y ago
  And udevd used to be it's own stand-alone daemon which didn't need systemd at all, but for some reason it is now essentially tied to it. * https://en.wikipedia.org/wiki/Udev#History https://en.wikipedia.org/wiki/Udev#History * https://en.wikipedia.org/wiki/Eudev https://en.wikipedia.org/wiki/Eudev
throw0101a 5y ago
So I can take systemd-timesyncd and run it on systemd-less Devuan or FreeBSD? systemd-resolved? systemd-networkd?