Here’s the Deal
Slant is powered by a community that helps you make informed decisions. Tell us what you’re passionate about to get your personalized feed and help others.
One of the runit project's principles is to keep the code size small. As of version 1.0.0 of runit, the runit.c source contains 330 lines of code; the runsvdir.c source is 274 lines of code, the runsv.c source 509. This minimizes the possibility of bugs introduced by programmer's fault, and makes it more easy for security related people to proofread the source code. The runit core programs have a very small memory footprint and do not allocate memory dynamically. See More
I use runit with Artix Linux. It's fast and it works. See More
Yoši Yoda's Experience
I'm the current maintainer (yes, the con of it not being supported is not QUITE truth), so I'll be honest and state a bit of bias there. Right now, I'm booting Yocto Embedded Linux distributions using runit thanks to meta-runit. It just simply works. It doesn't expose attack faces on your embedded devices like systemd DOES. It's easier to approach, easier to figure out how to drive it properly. See More
Frank Earl's Experience
So simple to use yet effective. Everything runs fast while also being stable. See More
Every init script spawns at least sh/dash/bash, and probably also additional processes such as cat, echo, start-stop-daemon, etc, just to start a single daemon that may not even be needed at the time of boot. This massive overhead results in poor performance, and is a killer for embedded systems. See More
Every init script needs to reinvent the wheel for every script: argument processing, start/stop/restart/reload/status/whatever processing, finding/clearing/creating PID files, sourcing defaults, building and setting configuration options, so on and so forth. See More
One of the main argument that people who are against using systemd is that it does not follow on of UNIX'S core philosophies. 'Do one thing and do it well', instead systemd represents a collection of dozens of tightly coupled libraries. With responsibilities that exceed those of a simple init system because it also tries to handle things like device management, power management, mount points, cron, encryption, syslog, network configuration etc... See More
Systemd is the default init system for most popular Linux distributions (Arch, Debian, Ubuntu, openSUSE, Fedora, etc.) Therefore there is an insane amount of support behind Systemd. Choosing Systemd means running with the herd, which comes with it's pros and few (or none for some people) cons. See More
Systemd is basically one of the main reasons why I switched back to Windows as my main operating system after using 10 years of Linux only. Its just hilarious everytime I update systemd somethink breaks eg I've get dropped to the emergency console for some stupid reason. or a start/stop job is running for a few minutes. See More
Holo Deck's Experience
It tries to do too much. I don't think most people who use systemd are even aware of most of the features as they don't really use them. It makes it really complicated to deal with sometimes, and it's possible that in a few years this project will be a nightmare to maintain, and with that the users of it will start to feel the fallout. See More
Help millions of people make better decisions.
Each month, over 2.8 million people use Slant to find the best products and share their knowledge. Pick the tags you’re passionate about to get a personalized feed and begin contributing your knowledge.