Re:PulseAudio and Systemd Creator, Lennart Poettering, Repor...
by zozbot234 on Tuesday July 05, 2022 @04:59PM
(#31993613)
These "simple" use cases break when you need to do anything even slightly more complex than whatever the systemD designers envisioned for the user. And if you try to submit an issue upstream, the typical response is "you're holding it wrong" or equivalent. This lack of a consistent design might be excusable when first trying to support a bunch of entirely novel use cases, but let's not pretend that it doesn't come with serious drawbacks.
[ Parent
| on HN ]
Re:PulseAudio and Systemd Creator, Lennart Poettering, Repor...
by ElectricalUnion on Tuesday July 05, 2022 @05:29PM
(#31993971)
These "simple" use cases break when you need to do anything even slightly more complex than whatever the sysvinit scripts you copied envisioned.
FTFY
systemd might be sad but makes the simple case simple. sysvinit makes everything complex and error prone.
Re:PulseAudio and Systemd Creator, Lennart Poettering, Repor...
by sam_lowry_ on Wednesday July 06, 2022 @05:03AM
(#31998468)
sysvinit could be debugged, at least. I tried to debug a couple of systemd edge cases with Pottering, communicating over Github Issues, but he lost interest very quickly.
To his, credit he is reactive until he decides the issue is not worth his time.
To his discredit, he made himself into a giant bottleneck. Random systemd users can not easily understand it.