> I just want to ask if you know of ANYONE, who has completely audited
systemd in its entirety at all.
To my knowledge, there has never been a single person who has audited the
entirety of Linux. It just doesn't work that way. With a large project like
Linux or systemd, everyone works on a particular part (or particular parts)
they are interested in.
If you think that's a problem, then by all means, trove through the entire
systemd codebase and check all of it. While you're at it, do the same for
Linux. No one is stopping you, because it's libre.
> OR if anyone has successfully forked systemd for any reason.
I don't think anyone has ever wanted to. All the systemd haters hate it
because it's systemd, not for actual technical reasons. It's just another
form of identity politics nonsense.
But if someone wanted to, of course they could do so. All of systemd is under
GPLv3+, a libre license.
> Although, this is the fault of the distributions forcing systemd more than
systemd devs themselves.
Nobody is "forcing" anything. You don't have to use Debian, or if you're
currently using an old version of Debian and don't like the update that's
coming, you don't have to upgrade.
What you're actually talking about is having a default program installed to
do a job and not going to lengths to make sure that other possible programs
can be used. So by that logic, Linux (the kernel) is being "forced" onto the
users of almost every GNU/Linux distro. Many distros don't even offer an
option for kernels other than Linux. The only ones I can think of right now
that do are Debian and Arch.
Regarding init systems, the current setup with systemd on Debian is exactly
the same as its previous setup with SysV-init, or Guix's setup with GNU
Shepherd, or Ubuntu 14.04's setup with Upstart, just to name a few. No distro
goes to lengths to give options for different init systems in a particular
distro because that's not a productive thing to do.
> try and remove all systemd components from a debian install. I doubt you
will succeed without a lot of irritations, and some sort of guide.
If so many programs depend on systemd (which, I might add, has nothing to do
with the actions of either Debian or the systemd developers), then perhaps it
was right for Debian to switch to systemd by default.
> This of course includes libsystemd0.
Why are you opposed to such a tiny library being installed on your system?
It's not even the init system systemd provides, just an API for everything in
systemd other software might want to use. Not having it installed means that
any program with even optional interfaces to systemd has to be rejected, and
that's a lot of useful software.
