I've felt that sisvinit is really all you need for a laptop or desktop, or possibly even a stand alone server.
But, after looking around, I took the path of least resistance and began using distros that use systemd.
Systemd has a lot of issues. It's monolithic. They went and built something that is very flexible, and then used it a way that hardly utilizes it. It is way more than someone with a laptop, desktop, or server really needs. It solves a problem that is really only a problem for someone who has lots of systems to maintain each of which may have different configurations. Unfortunately, they didn't make this as easy as it should be; see not using flexibility previouly mentioned.
It does get around some of the awkwardness of rc.local, for example. If only I could get it to work. That was an issue with rc.local too,as I recall.
I'm thinking that if I get some time, I'll play around with it.
On Sat, Nov 08, 2025 at 07:09:03AM -0800, Charles Polisher wrote:
On 11/7/25 12:45, Brian E. Lavender wrote:
Install Fedora 43 from a clean install and systemd should work fine. Is Slackware still on non systemd?
Brian
Slackware is still running on sysvinit. Years of experience with Slackware, Fedora, Ubuntu, CentOS, Red Hat, FreeBSD, ... haven't has a problem with sysvinit, have spent dozens of hours "supporting" systemd. I haven't experienced any tangible benefit, but from previous posts, and private conversations on this topic, you do. Could it be because you're a laptop user? I believe that laptops would be ideal for me, except that the keyboards are always a non-starter. I haven't ever tried a laptop keyboard that didn't make my fingers feel retarded.
-- Chuck Polisher _______________________________________________ Lug-nuts mailing list -- lug-nuts@bigbrie.com To unsubscribe send an email to lug-nuts-leave@bigbrie.com