|
|
|
|
|
by binaryapparatus
3175 days ago
|
|
This is not even the best source of information but it shows the same trend I was spotting:
https://suckless.org/sucks/systemd There are similar sources on the internet that claim the same thing in different forms. Every single bad systemd decision is not terribly bad on its own, but when observed as a process they result in a horribly wrong and very insecure system. With systemd, there i crawling revolution of bad ideas, bad implementation and taking over of everything that was great in linux. When you try discussing any of those items separately you'll be redirected to 'technical discussion' and you can't really technically discuss conceptually wrong system. With bad concept it doesn't really matter how technically good or bad implementation is. Maybe the best telling thread, in order to understand how pushy and deceptive whole systemd is, is watching how Greg Kroah-Hartman tried to sneak kdbus into a kernel:
https://lkml.org/lkml/2015/4/13/645 It is very long mailing list thread and GH is not officially part of the systemd team -- only that he is, unofficially. He claims that kdbus brings great benefits and speedup only that he can't prove it. Every questioning of a very wrong concept is met by requesting of 'technical discussion'. If you have patience just read that lkml thread and you'll see the same sneaky politics of pushing things the same way that systemd people do it all the time. |
|
I remember of this long article, that, technically demonstrates that systemd is badly designed, as you said: http://blog.darknedgy.net/technology/2015/10/11/0/
Didn't read it entirely at the time as it dives really fast into the technical stuff and provides an ever growing flow of informations that you have to absorb to understand it correctly. Seeing people like you being so concerned with systemd makes me inclined to re-read it fully.
And why FreeBSD and not voidlinux or something in this fashion ? More secure ? More mature ? Will never be subject to such issues ?