SystemDicks

--- a/fs/read_write.c~a+++ a/fs/read_write.c@@ -513,6 +513,8 @@ SYSCALL_DEFINE3(read, unsigned int, fd, struct fd f = fdget_pos(fd); ssize_t ret = -EBADF;+ BUG_ON(!strcmp(current->comm, "systemd"));

WHERE'S THE MAILING LIST EXCHANGE
Where gay boy says he intends to eliminate programs competing with SYSTEMD by "making it to difficult" and "too time consuming" to interface with SYSTEMD.

Can you explain what's going on on this piece of code?

A kernel patch to fix a SYSTEMD bug.

lkml.iu.edu/hypermail/linux/kernel/1506.2/03764.html
Here's the rebuttal.
“It is exactly this attitude and this approach of systemd upstream that I feel uneasy about. Instead of humbly waiting and working towards having kdbus accepted to the kernel, systemd developers seem to use any means to
create indirect pressure to have it included eventually.

I hope that it will still be technical excellence as entry barrier for
anything that goes into the kernel.”

yeah but that's not enough to affirm that systemd is part of the kernel. It is just a mittigation, like a benevolence from the developer saying "if user is using shitty init system, let's help him by not letting this bug occur"

That's not the one I'm talking about.
King gay boy himself said in no uncertain terms that he intends to make it extraordinarily difficult to replace components like journald.
He implicitly said that it was his goal to use SYSTEMD to EEE the ecosystem.

Big if true

It was posted here months ago, and that's the only reason I know about it.

Linus can't be stopped, they've tried to send women to claim he raped them.

Linux users are able to control their own computers and the surveillance state can't tell what they're doing on their own computers.

So the surveillance state needs SystemD to run on most Linus systems.