76
systemd(ont) (www.arscyni.cc)
submitted 2 days ago* (last edited 2 days ago) by arsCynic@piefed.social to c/linux@lemmy.ml

Because of the ubiquity, nay, monopoly of systemd I always assumed it was miles ahead of other init systems. Nope. I've been using a non-systemd environment for a while and must say I'm surprised by how little breaks, i.e., next to nothing. Moreover, boot and shutdown times are faster, and more of that good stuff. I suggest trying it out.

https://nosystemd.org/.

top 50 comments
sorted by: hot top controversial new old
[-] mactan@lemmy.ml 26 points 1 day ago

steady hand and a magnetized needle is all I need. kernel is bloat

[-] gandalf_der_12te@discuss.tchncs.de 1 points 15 hours ago

in theory systemd is faster because it can do things in parallel

[-] juipeltje@lemmy.world 14 points 1 day ago

I'm sure this post isn't going to be controversial at all lol

[-] fozid@feddit.uk 17 points 1 day ago

After over a decade using systemd in arch and Debian, I never had any direct issues with it. However, I never truly got my head around it or got comfortable with how it functioned. I recently swapped arch for void which uses runit, and after over a month using it I to an amazed both how clean and simple it is, how everything just works, how easy to interact and use runit is and am blown away by boot and shutdown times. My arch / systemd setup was heavily optimised for boot, and I thought was quick, but runit starts in about 4 seconds and shutdown is about 2 seconds.

[-] sudoer777@lemmy.ml 10 points 1 day ago

Systemd has been putting a lot of effort into eliminating the need for SUID binaries with run0 and polkit integrations, so I'm curious if other init systems are doing anything similar.

[-] PseudoSpock@lemmy.dbzer0.com 30 points 1 day ago

Boot speed is meaningless. Having to almost never reboot is everything.

[-] pastermil@sh.itjust.works 3 points 1 day ago
[-] thingsiplay@lemmy.ml 4 points 1 day ago

Sleep doesn't work well in some environments, like right now my current one using AMD+AMD hardware on EndeavourOS. Therefore I do boot. And couldn't care less for 10 seconds faster or slower boot times.

[-] pastermil@sh.itjust.works 2 points 1 day ago

Lol, I meant this to be a tongue-in-cheek saying

[-] thingsiplay@lemmy.ml 3 points 1 day ago

Oh... :D But you were right.

load more comments (1 replies)
[-] azimir@lemmy.ml 35 points 1 day ago

Use what works for you.

Develop what scratches your itch.

Don't tell OSS devs who are volunteering unpaid labor what they should do for you.

If you want a solution that's non-systemd go for it. If it doesn't exist make it or pay someone to do so. Write from scratch or fork a project and get to work. That's the way of the Bazaar.

I'll be in my unenlightened "things work for me good enough" Linux world using what works. Systemd is fine and rarely gives me problems. Actually, I'm not even sure I can remember any.

Huge thank you's to the devs who make this all possible. You rock!

[-] Liketearsinrain@lemmy.ml 17 points 1 day ago

Systemd is developed primarily by paid developers.

[-] zurchpet@lemmy.ml 4 points 1 day ago

I think that is a good thing, isn't it?

[-] Liketearsinrain@lemmy.ml 3 points 1 day ago

Of course it is, I was just addressing the part about "unpaid volunteers". I think it's fair game to criticize a corporation throwing their weight around to push their tools on the ecosystem.

load more comments (23 replies)
[-] False@lemmy.world 51 points 1 day ago

I've never had systemd break either

[-] greyscale@lemmy.grey.ooo 11 points 1 day ago

I have. Never had your machine just sit there and refuse to boot because a network share is down? Or because the wifi isn't connected yet? Or because its waiting on some nebulous thing until timeout..

Never had to crawl through journalctl to diagnose things and wanted to claw your own eyes out in frustration?

You are a fortunate person.

[-] Wolf314159@startrek.website 3 points 22 hours ago

Ever really destroyed your server because the it needed were available? I have. It was so much worse than a boot process that froze.

If Systemd was pausing due to a network share being down, it's only because I (or you) told it to do exactly that. There are lots of good reasons to delay the boot process until all drives the system expects to be there are actually there or the network is up. Cleaning up the mess that happens when the system does not check these kinds of things at boot is so much worse. It's never really some nebulous thing. Like it or not, intentional or not, the machine is doing exactly what you asked it to do and a delayed boot or a boot halted until you can solve the real problem is almost always better (or at least safer) than the alternatives. I've experienced all the things you've mentioned, dealt with each of those issues, and it was so much more of a hassle to diagnose before Systemd.

[-] Archr@lemmy.world 12 points 1 day ago

If you are having those issues with booting maybe it is because you configured your network share incorrectly? If you are waiting on shutdown timeouts for something then just go edit the timeout. systemctl edit <stuck thing>.

Typically when I crawl through journald it is to diagnose a problem with a specific application. Actually, the fact that those logs are easily accessible in a centralized place with easy to understand commands to access them is a reason why systemd (or more specifically systemd-journald) is so great.

The only times that I have had major issues like that was either because (A) I misconfigured something or (B) a package came misconfigured.

load more comments (2 replies)
[-] KernelTale@programming.dev 3 points 1 day ago

My system once refused to boot, because I deleted a partition and didn't remove it from fstab. Thankfully it was an easy and fast fix but I would expect it to just boot and give an error.

[-] vaionko@sopuli.xyz 3 points 1 day ago

That's why I always put a nofail option for all my drives except the boot drive

load more comments (1 replies)
load more comments (4 replies)
load more comments (1 replies)
[-] balsoft@lemmy.ml 32 points 2 days ago

Honestly for desktop usage it doesn't really matter. All inits have their idiosyncrasies ("A stop job is running for Session"/logging hell on openrc/etc). But for managing a fleet of bare-metal servers I find systemd to be the best, most polished one out of the lot.

load more comments (4 replies)
[-] DieserTypMatthias@lemmy.ml 25 points 2 days ago* (last edited 2 days ago)
for script in $(find /etc/init/start); do
    exec $script &
done

sleep

Undoubtedly the best init system that exists. No fluff, just starts services.

[-] infeeeee@lemmy.zip 35 points 2 days ago

Why do you need services at all? Just start each program when you need it. Shell is bloat.

[-] DieserTypMatthias@lemmy.ml 4 points 1 day ago
[-] Liketearsinrain@lemmy.ml 3 points 1 day ago

Yeah but lacks some functionality. I prefer /bin/emacs so I can edit text as well as run commands. EXWM is bloat.

[-] FauxLiving@lemmy.world 17 points 1 day ago

You only need programs if you're unhappy with the current state of your life. Delete computer, become enlightened.

load more comments (1 replies)
[-] greyscale@lemmy.grey.ooo 11 points 1 day ago

I mean.. thats kinda what runit does.

[-] TCB13@lemmy.world 15 points 1 day ago

Systemd is mile ahead of the others, thing is that solves problems that you most likely don’t have or even know that exist. To boot a regular machine or small server pretty much any init system is good.

load more comments
view more: next ›
this post was submitted on 14 Apr 2026
76 points (69.6% liked)

Linux

63789 readers
741 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

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago
MODERATORS