this post was submitted on 28 Jul 2025
62 points (90.8% liked)
Linux
8662 readers
568 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I feel like this is just like systemd, those that want to stick to the old ways are very vocal but are a very small minority.
Edit - Sometimes I want to erase spell checks 1's and 0's.
100% a system D like issue. And I get it. People tend to hate change. The old init scripts work okay back in the day. And if you're familiar with them I can see why you wouldn't want it to change. But system D really has brought something to the game. It's so much easier to enable disable services. No having to dig through init scripts trying to find the one you're looking for which might be called through a script of a script of a script.
And while I hate to see fragmentation between the Linux and BSD space. Part of that is on the BSD space. Reluctance to do anything different than the way it was always done can and will hold you back. Not that BSD has ever been fragment free on its own.
The big reason I personally dislike Systemd is bloat. It takes me 6 seconds to boot a windows 11 VM, it takes 20+ with Systemd, and it takes 6 seconds with dinit. On real machines I frequently hit 40 seconds with systemd. Now is that enough of a problem that I am going to switch to Windows (ugh) or Chimera/Artix, probably no. I still find it very annoying.
That's not normal. Unless you're using an HDD, but then Windows wouldn't boot that fast.
Check the output of
systemd-analyze blame.I have tried. Nothing worked. I also experience the same slow booting on every machine+systemd, with the same resulting slow boot up. Even friends have mentioned to me the slow boot times compared to Windows.
I boot to login in probably under 5 seconds, so 30+ seconds seems like something is not configured correctly. And every Windows machine I've ever interacted with boots slow and updates even slower.
Idk what is wrong but every fresh install on any Systemd distro (Arch, Fedora, Debian, openSUSE) has the same slow boot on every device I have tried. I have never seen a 5 second boot on anything else but dinit.
Oh, and my disk is a modern M.2 SSD for my workstation.
I did a fresh install of fedora in a VM given 4 cores, 16gb ram, and storage on an NVME SSD. Finally I am getting a reasonable boot time of 6.5 seconds. But on bare metal I can't get anywhere close to that. Firmware alone takes 15 seconds. Either way, now I know that it isn't a "Systemd problem", just that only Systemd gives me this problem.
If you actually want to fuss with it you could always try some of the stuff from the Holy Wiki and see if it makes a difference. Sometimes it's just "gremlins" though.
I ironically had a similar issue with moving to Wayland from X. I did everything I saw documented to make it work and it just either flat out didn't, or performance was ass. Then I think when I had read about Gnome's future plans to drop X I figured I needed to give it another go. In the end I'm not sure what made the difference (update/config/etc.), but I'm using Wayland now and performance seems the same/better and all is good. My install is also probably close to a decade old (or more - I have moved it between at least 3 disks) at this point so I also have cruft out the ass lol.
Edit - Got curious and decided to look and this install is dated 2013-02-24, so longer than I thought.