this post was submitted on 06 Aug 2025
388 points (94.5% liked)
linuxmemes
27084 readers
1973 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
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
It's almost as if people think systemd is one massive executable rather than a suite of tools
Nah, it's a single executable, like GNU.
All that happens at boot is that linux.exe calls systemd.exe, uses all your system resources making your machine unusable bloat.
when you first boot Systemd calls back to Redhat HQ: "Mr Pottering, we got him"
When did you last update your system? It should call Microsoft, not Red Hat.
None of this stuff for me. I prefer one tool doing one thing, like busybox
I'm worried some might not get this joke
Initramfs is just a executable
Prove me wrong
It's executables all the way down
Yes, GNU.exe, I know it well.
From all the hate you see, it does look like that. It is not?
The answer is more complex than a simple yes/no. Fortunately, an actual Arch Linux maintainer shared their experience with init scripts and why it was necessary to switch to systemd: https://redlib.privacyredirect.com/r/archlinux/comments/4lzxs3/why_did_archlinux_embrace_systemd/?
This line is particularly great:
Other than that, and especially in the case of Arch Linux, nobody is forcing anybody to use any other component of systemd, or as proven by the likes of Artix and Devuan, systemd itself.
That was an interesting and enlightening read. Thanks!
Well it is also a massive executable in the mix there
Did you accidentally forget A) the .so files these binaries link against and B) the actual systemd daemon binary?
Are you intentionally misrepresenting this or are you actually missing these? Also: This isn't about diskspace. Obviously every halfway modern PC can provide the disk space to house the systemd binaries. Disk is cheap but crucially not necessarily tied to complexity. A simple application can take Gigs and still be simple if it includes a lot of resources (graphical, audio, whatever). And a very complex thing can "only" take a few megabytes if it only includes code. Like systemd does.
Note that I am a (mostly) happy user of systemd. I am just annoyed at people misrepresenting facts to fight anti-systemd-bullshit.
It's weird ldd didn't find libssytemd.so ! I have an old system, apparently libsystemd-core and libsystemd-shared weren't a thing back in 2021 on ... ubuntu focal
Sorry but there is a libsystemd-shared listed in your screenshot
ok well still not over 10 meg, I don't know, doesn't seem like bloat to me still
As I said: I didn't mean massive in the sense of "disk space is an expensive resource". Disk is cheap nowadays. I meant massive as in "there is a lot of code and by that a lot of complexity in this one binary". You just inferred I meant bloat. I get that that is my fault for not specifying it the first time But I already explained I didn't mean that so I don't really get why you keep riding that 10 meg point.
Ok, sorry I don't understand the problem, beyond the loss of modularity, that you can pick and choose different components for service/network/login/logging and timers but even if they were each distinct entities, would they really be less complex as a whole ?
These core system might even be more complex if they had to accommodate modular ways of doing things instead of relying on a uniform and consistent framework between them.
I agree from something like an embed system, like this openwrt WAP system that has just 4 megs of flash for the entire thing including a very complete web user interface, 10 meg for just these core services is giganormous and systemd is inappropriate. But for the average server and desktop with so much as dozens of megs of disk space, I feel the single coherent, reliable, universal systemd is pretty great once you learn it's basic logic. I feel it's actually less complex to use than what came before it, more predictable, more comfortable than sysv which generally lacked structure.
I dont have a problem with systemd. I have a problem with people claiming systemd doesn't have a massive non-modular blob of code at it's core. There is no need to misrepresent what systemd is to deflect systemd critics.
Again, please read what I am writing. I don't care about the disk space. And I don't have a problem with systemd itself.
An inbred set of separate entities right out of x-files "home" , that can only coexist with one another in a toxic bug-eyed gang? Yeah, it's "separate" pieces.
Now go mount a volume the normal way.
I still write my mounts in fstab
Wait doesn't everyone
/etc/systemd/system/mnt-nfs.mount
And the reason you'll want to do this is that it exposes FS mounts in the service dependency tree, so e.g. you can delay starting PostgreSQL until after you've mounted the network share that it's using as a backing store, while letting unrelated tasks start concurrently.
If all you want to do is pass some special mount flags (e.g.
x-systemd.automount) then fstab is the way, after all it's still systemd that's parsing and managing it.oh! maybe it's the perfect chance to ask. what do you do with your mounted shares so that processes trying to access it do not hang when the server is unreachable?
mostly I would prefer if that directory read would just fail but anything is better, except unmounting.
Add -o hard
And if youre using nfsv3 add retrans=5
Nfsv4 doesbt really need retrans but it still worls.
That has worked perfectly for me.
does retrains have any effect with hard? this is what man nfs says:
also, do you know what can I do with CIFS/SMB? I have most of my shares through samba :/
Oh maybe retrans doesn't do anything with hard.
Cifs has some options too, it is easier to deal with user ids than NFS. I just had Claude AI tell me options
Good question!
In the Home Operations Discord there's some very smart people who solved this problem inside kubernetes by checking if their NAS is online (through a Prometheus exporter named node exporter) and then scaling down their workloads that use it, automatically, using KEDA (an autoscaler for kubernetes)
Depending on how your processes are orchestrated, you might be able to do something similar?
Source: https://github.com/onedr0p/home-ops/pull/9334/files
well that's also interesting, but I mainly experience this problem on my desktop. there was a plasma version when even the taskbar panel got frozen, and the kde file manager, double commander too for like a minute, every time they try to do anything with an unreachable network drive. and its even worse on my laptop so there I just don't mount my shares anymore.
I have been wondering how does windows do it, and programs made for windows, because this is a nonissue there (though windows has its fair share of problems with network shares though..). maybe they just learned to do all IO ops on a different thread..
I'm not even aware of another way