Linux Questions

4052 readers

41 users here now

Linux questions Rules (in addition of the Lemmy.zip rules)

stay on topic
be nice (no name calling)
do not post long blocks of text such as logs
do not delete your posts
only post questions (no information posts)

Tips for giving and receiving help

be as clear and specific
say thank you if a solution works
verify your solutions before posting them as facts.

Any rule violations will result in disciplinary actions

founded 3 years ago

MODERATORS

possiblylinux127@lemmy.zip

Why use something other than SystemD? (piefed.world)

submitted 2 days ago by daggermoon@piefed.world to c/linuxquestions@lemmy.zip

29 comments fedilink hide all child comments

I'll admit I have used Artix, Peppermint OS (Devuan), and Void Linux because I thought the idea of a SystemDless distro sounded cool. It wasn't because I had a problem with SystemD. It's more so that I love that numerous options exist for different system components. For me it's sad to see that certain features or applications require SystemD be present. I like SystemD, just to be clear. I also like the freedom to choose. Maybe, i'm missing something. What do y'all think? What do you use and why? If you use OpenRC or something, why? I'm guessing most people use SystemD and don't give it any thought which is fair.

you are viewing a single comment's thread
view the rest of the comments

[–] 9point6@lemmy.world 14 points 2 days ago (3 children)

The main practical reason to not use it is if you don't need it and have an environment or task that would benefit you going for something else.

A classic example is containers, if they do have an init system at all, it's usually not systemd but something much simpler, because the environment/task doesn't need it and there's a memory and storage benefit to not shipping the extra bulk

Void uses runit because they want to optimise for quick and lightweight without caring about wide compatibility, so that's a choice aligning with their philosophy.

[–] moonpiedumplings@programming.dev 1 points 1 day ago

if they do have an init system at all, it’s usually not systemd but something much simpler, because the environment/task doesn’t need it and there’s a memory and storage benefit to not shipping the extra bulk

Systemd often just straight up doesn't work in containers due to containers having security restrictions that prevent processes in them from accessing certain parts of the Linux kernel. Systemd tries very hard to be a container manager (nspawn, portable services, cgroups controls, and so on), whereas other init systems don't do this, making them work inside containers

load more comments (2 replies)