Systemd is no longer just an init system, but the project began with Poettering’s dislike of other init systems. I use systemd and I do not like its performance (too slow in some cases).
The tragedy is that being an end-user, it is ridiculously hard to replace systemd on “regular” distros. Admittedly, Debian can be moved back to sysVinit without backbreaking work, but the fact is that distros don’t seem to have any intention of providing choice, making applications assume that systemd exists wherever they will be installed. That is the complaint I have against the Linux community
Most distros independently decided that SystemD was superior. They had a choice and they chose. Distros are often maintained by volunteers in their free time. Same with software that depends on it. Expecting them to provide poor irrelevant choices is not how open source works. You’re passing on your backbreaking work onto other people. If you want another option, you give your time to make it happen.
no. Processes have a life cycle other than init. Fire and forget with bash scripts is backwards.
I am no expert on this and could not do this answer justice. A quick search will provide a better and more detailed answer. That is if you are willing to consider that SystemD provides benefits. The way you wrote your question gives me vibes that you do not want to, so this debate would be fruitless.
Explain how other init systems are necessarily worse than systemd
SystemD is not an init system. It provides that functionality, but processes have more life cycle steps than just initialize.
When you accept that, you realise that you cannot compare them.
SystemD provides functionality that they don’t. Of course those that refuse to consider this will just claim it’s bloat. To some DE’s are bloat.
Systemd is no longer just an init system, but the project began with Poettering’s dislike of other init systems. I use systemd and I do not like its performance (too slow in some cases).
The tragedy is that being an end-user, it is ridiculously hard to replace systemd on “regular” distros. Admittedly, Debian can be moved back to sysVinit without backbreaking work, but the fact is that distros don’t seem to have any intention of providing choice, making applications assume that systemd exists wherever they will be installed. That is the complaint I have against the Linux community
There is Alpine and Void Linux which are commonly known of. Plus more: https://en.m.wikipedia.org/wiki/Category:Linux_distributions_without_systemd
Most distros independently decided that SystemD was superior. They had a choice and they chose. Distros are often maintained by volunteers in their free time. Same with software that depends on it. Expecting them to provide poor irrelevant choices is not how open source works. You’re passing on your backbreaking work onto other people. If you want another option, you give your time to make it happen.
Two questions:
Sure, the alternative init systems don’t provide non init functionalities, but other software probably does.
no. Processes have a life cycle other than init. Fire and forget with bash scripts is backwards.
I am no expert on this and could not do this answer justice. A quick search will provide a better and more detailed answer. That is if you are willing to consider that SystemD provides benefits. The way you wrote your question gives me vibes that you do not want to, so this debate would be fruitless.
If you’re genuinely curious Benno Rice has a great talk on SystemD: https://m.youtube.com/watch?v=o_AIw9bGogo&pp=2AHFBpACAQ%3D%3D