this post was submitted on 09 Jul 2025
258 points (85.8% liked)
Linux
56331 readers
793 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
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I totally agree. I used to hate systemd for breaking the traditional Unix philosophy, but the reality is that a tight init and service-tracking integration tool really was required. I work with and appreciate systemd every day now. It certainly didn't make things simplier and easier to debug, but it goes a long way towards making a Linux system predictable and consistent.
Poettering can go fuck himself though - and for PulseAudio too. I suspect half of the hate systemd attracted over the years was really because of this idiot.
Or none of those.
Oh. My NIC didn't 'start' because systemd and network manager are fighting again? Neet.
I don't know why they are downvoting you, it's true. I'm dealing with this kind of problem currently.. sometimes the boot lasts forever to the point that I have to use AltGr+SysRq commands to force kill everything.. other times it simply boots as normal. It's not consistent at all.
At least before with the old init it was relatively simple to dig into the scripts and make changes to them.. I feel now with systemd it's a lot more opaque and harder to deal with. I wouldn't even know how to approach the problem,
systemd-analyze blamedoes not help, since the times I actually get to boot look normal. But I do believe it must have to do with the mountpoints because often they are what takes the longest. Any advice on what should I do would be welcome.Also, I have a separate Bazzite install in my living room TV, and while that one does not get locked, sometimes NetworkManager simply is not running after boot... I got fed up to the point that I wrote a workaround by creating a rc.local script to have it run, so I can have it available reliably when the system starts (that fixed it.. though some cifs mountpoints often do not get mounted.. so I'm considering adding the mount command to the same rc.local script too....).
You can play around with the mount option
nofail, if that's set, systemd will not wait for the mount point to be ready and continue booting normally. Can be useful with HDDs that take a while to spin up and aren't needed for the boot process (e.g. backup drives, etc.).Another thing to look out for: SDCards or USB flash drives that might randomly fail to "spin up" and hang, unplugging those helps.
Thanks! I'll try with
nofailand see if the lockups stop!Honestly, that could be it now that you mention it.. I have had for a while an external hard drive plugged in that I've used for some backups.