Systemd, 10 years later (2020)

Re:Systemd, 10 years later (2020) by throwaway984393 on Saturday January 08, 2022 @05:07PM (#29856904)

Part of it was political, but it was also just practical. Poettering's designs are some of the worst for usability I've ever seen. They technically work, but you need a million StackOverflow Q&As to figure out how to get anything done or solve the many common problems.

It's like somebody decided that the problem with Linux was it wasn't complicated enough. And then everbody just went with it.

[ Parent | on HN ]

Re:Systemd, 10 years later (2020) by erik_seaberg on Saturday January 08, 2022 @07:32PM (#29858385)

I keep coming back to the https://news.ycombinator.com/item?id=19023885 issue. There’s a default setting somewhere that makes systemd knowingly kill normal user processes it did not start. Why does that exist? It was never init’s job, and init is not something end users should have to be aware of to run stuff with POSIX nohup.

[ Parent | on HN ]

Re:Systemd, 10 years later (2020) by throwaway984393 on Sunday January 09, 2022 @11:26AM (#29864667)

Jesus. I didn't know about that, but it totally makes sense. Like when systemd devs told Linus he should change his kernel to fix a bug in systemd.

[ Parent | on HN ]