I'm using a distribution that defaults to systemd. Would switching to something like OpenRC or runit offer a noticeable benefit, or is it mostly a matter of preference? I'm more interested in practical tradeoffs than ideological arguments.
Is there a practical reason to switch away from systemd?
Answers
If your system works and you don't have a specific problem to solve, sticking with systemd is probably the easiest option. Your distribution's packages, documentation and troubleshooting guides are likely to match its default setup.
Switching just to switch can mean extra work maintaining services and figuring out instructions written for a different init system.
Reply to this answer
There can be benefits if you prefer a smaller, simpler setup or want to reduce resource use. OpenRC and runit are worth exploring for those reasons, especially on a machine where resources are tight.
How much you save depends on the distribution and what services are actually running. I wouldn't assume changing the init system alone will make a noticeable difference without measuring it.
Reply to this answer
Systemd is more than the process that starts services. It also includes tools for things like logging and service management. Some people prefer separate tools and plain-text logs, while others like having an integrated set of tools.
That's a real usability difference, not just a debate over labels. Whether it matters to you depends on which tools you want to administer and troubleshoot.
maple.keyhole:
And a systemd-based distribution doesn't necessarily run every component of the suite. It's worth checking the actual setup before comparing it with an alternative.
Reply to this answer
There is also a practical upside to the integration. Managing services and reacting to devices appearing after boot can be easier when the distribution already has those pieces configured to work together. A simpler init system can do the job too, but the surrounding setup matters.
Reply to this answer
Trying another init system can be worthwhile just to learn how your system starts services. I'd test a distribution that supports it out of the box in a virtual machine rather than replacing the init system on a working installation. That lets you compare the day-to-day tools without risking your existing setup.
Reply to this answer
Add your answer
Answers are reviewed before publication.
quarterpast_typing:
That makes sense. I was wondering whether there was a practical payoff I was missing.