this post was submitted on 11 Jul 2026
22 points (100.0% liked)
Linux
66349 readers
363 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 7 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You can just try them out in a VM if you're interested. Systemd can become quite a deep rabbit hole, but most of the others are quite simple and best learnt by doing.
I realize this is the best option, since it centers my experience and needs better than anyone else's summary, but what to do if I don't have the time to daily drive enough init systems long enough to understand the scope and limitations of each?
E.g. Gentoo's wiki has a comparison chart of all the systems I'm aware of, but I don't know what some of the rows mean, so I would have to daily drive multiple types to get a feel for what it's like with and without those options and how that affects me as an end-user. It also doesn't include metrics that often get referenced but not quantified in the comparisons I find (stuff like boot times)
Furthermore, the only two times I've tried to switch out the init system on my PC, I've somehow managed to bork things so bad I had to do a fresh reinstall. Yes, I could do troubleshooting, but that's even more hours (or even days) of downtime up front.
All this to say: I'm just looking for a little bit of a shorcut to reduce the amount of documentation I have to read, and tweaking I'll end up doing.
I think if you're at the point of poweruser where you're deciding an init system, you probably should just try them out in VMs. It doesn't have to take loads of time. Install an OS, try writing some basic services, try doing some basic config for your use-case.
For the vast majority of users, they'll never have this problem, because they'll just use whatever init system comes with their OS. I know some distros give init freedom, but most are locked in to one or another init. The fact that you have this problem suggests that either you're using the wrong distro and should switch to one that chooses for you (or just pick based on one-line descriptions), or it'd be worth your time to spend a day or two poking around with the init systems under consideration in VMs.
Unfortunately, you do what everybody else does. You use your reading, patience and time to research test and try various options over the course of weeks, months and years until you get experienced and knowledgeable about Linux and the ever changing options and configurations. There is no ultimate manual that tells you everything there is to know about Linux.