altoid via Dng - 28.06.24, 13:14:29 CEST:
> To finish and illustrate the point, I'll quote from a post (not mine)
> at The Register from 05/2017, more than seven years ago:
>
> "Systemd also has its dirty fingers into other parts of the system.
> As a replacement for sysvinit it is supposed to be an init system,
> but because its scope goes far beyond the initialization phase (and
> it doesn't let you take the good without the bad) it has become a
> dependency for many userspace programs that should never have any
> reason to interact with the init system at all, making it harder to
> use those programs on a non-systemd system."

That for sure is an accurate assessment.

--
Martin