Glenn Holmer writes:
On 09/30/2016 07:41 AM, Sam Varshavchik wrote: > Pretty much says everything there is to say about systemd, in one > compact article: > > https://www.agwa.name/blog/post/how_to_crash_systemd_in_one_tweethttps://medium.com/@davidtstrauss/how-to-throw-a-tantrum-in-one-blog-post- c2ccaa58661d#.8cem83295
That response appears to be written by a systemd developer, so it's not exactly surprising. And the writer immediately goes into a contradiction:
# Things that interact regularly with PID 1 over a bus or socket but are # isolated by process and privileges. This includes a handful things, like # logind and the journal.
Which he had to begrudgingly admits later, is not exactly true:# This is a reasonable request, and I’ve been pushing for more modularity # around parsing for a while.
Except that he fails again. This is not about parsing. He then goes and builds a big house of cards, focusing on parsing, etc… The problem with a simple command crashing PID 1 is that it's just a parsing problem.
Year, right. This type of an intentional blind spot is quite typical, inside the systemd reality distortion field.
Besides, throwing a well-deserved temper tantrum is not such a bad thing.
Attachment:
pgpTjW33BkF85.pgp
Description: PGP signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
