> Now that systemd has wrecked all kinds of previously working stuff, and
many are beginning to realize the *impossibility* of getting systemd to
> work *with* linux -> I think this might have some effect this time
around.
Hello everybody,
I've been watching this discussion, quite curious what would come up and now that I have read some responses I would like to say that
1) I think some valid questions have been raised to which I have not seen ANY satisfactory answer that no doubt a person who truly understands the subject (unlike me) should be able to give. (though I might have missed some)
2) The responses with more or less subtle aggression and comments about the FORMAT of the original message greatly disquiet me as a user and "client" of the debian OS. Of course some formatting can help you better read the message but I was able to read it, I understand it as much as my education permits and I believe I possess only average intelligence, so I can't imagine why asterisks should be a problem for the "OS guys". I believe focusing on such unimportant things is only the sign of ego standing in the way of clear reasoning.
I would also like to ask something the people who dislike systemd (as there seem to be more). I am not very proficient with such internals of debian, but you say things like systemd breaks things and systemd has no unified design and sytemd is possibly a security risk. But can you give some easily reproducible examples or setups, code samples, cucumber scenarios, whatever, that could clearly demonstrate how systemd breaks anything? Otherwise it's very hard for me to judge anything if I can't play around with it and truly see for myself that it's so EVIL. Otherwise if you just personally disagree with the design of systemd and can't describe such a scenario, why not just migrate to Gentoo or BSD?