That udev is placed in the same source tree as systemd does not make systemd eat it and also doesn't mean that packages needing udev also suddenly needs systemd.

How can it be both monolithic and have many components? How in hell can you compare encryption with binary logs.

"offers only itself as a way to read them.": So that is why the format is fully described in detail?

And what the hell is "it encourages non-kernel systems to rely on it"?

Anyone who complains over overcomplexity or security have never ever really tried to understand just how SysVinit works or read it's source to begin with. If anything systemd makes it much less complex (a single unit file in a single place vs tons of links and overcomplex bash scripts all over /etc).

Perhaps all the "good technical complaints" are drowning in all the trolling, hatred and death treats? It sure looks that way anyway.

You do realise that Ubuntu haven't switched to systemd yey, so the troubles that you experience with sleep there have nothng to do with systemd.

What if someone attacking you by crashing sshd so you cannot ssh to it? And honestly if you are afraid of any of the things that you wrote, then simply disable the restart altogether. It's not like it's mandatory, systemd even has it disabled by default, it has to be enabled in the unit file for each service.

Proof to that?

Exactly which liberties does MariaDB take with your data?

Ah, that makes sense. I was referring to Swedish law since it was about the Pirate Bay case.

And the maximum for copyright infringement is 2 years.

You got that kind of backwards. The _minimum_ jail sentence for rape is 2 years, the maximum is 10.

Since exactly when is Skype FOSS?

So you just do not have a clue do you? If you even bothered to do any form of search you would have found out that it works exactly like I wrote. There is no httpd server in the systemd binaries, none in the journald binaries. But in a very specific binary called the journald gateway daemon, which have a single function (i.e expose the local logs via http). If you don't run that daemon (which is the default) then you won't run any http server at all no matter how much you cry about it. And if an attacker could start this daemon to get acccess to your holy log files, then you have other security issues with your set up that is way way worse. But don't let reality get in your way pal.

The init system is not not a part of it at all. The journald gateway deamon is a separate binary that does one thing and only one thing: it allows http access to the local log files. If the daemon does not run, which it doesn't unless it's manually activated, then it has no impact what so ever. So NO, the init system or even journald does not contain a web server.

And when does this happen? I haven't experienced it.