this post was submitted on 26 Feb 2025
291 points (100.0% liked)
linuxmemes
24211 readers
1123 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
3. Post Linux-related content
sudo
in Windows.4. No recent reposts
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
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.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
Maybe the arguments against systemd are issues of the past. I see people, hating systemd, bringing the same arguments of it being unstable, or constantly breaking, again and again.
However, I don't remember actually coming across any of those problems, or discussions about them, for the past 5+ years that I have been using Linux both for my computers and servers.
I have used Ubuntu, Debian, Fedora, Arch, Proxmox, NixOS. All of them use systemd.
They only problem I remember facing with systemd, which is actually never mentioned by anti-systemd people, is about its containers system, nspawn, which enables some security features by default. Those break things that tend to work with LXC without much tweaking. Docker, for example, may face issues running inside nspawn.
Systemd is actually way more reliable than other solutions. Forget things like cron and startup scripts. Systemd can monitor and automatically try to restart software.
Systemd hate mostly boils down to hating change
Been using systemd for at least 6 year now, and yes it is indeed quite stable.
But making startup services is hot garbage, and accessing system logs is even worse.
journalctl
is an unapproachable mess, and I really don't like the idea that systemd is kind of slowly replacing the linux kernel in its entirety.It doesnt affect my day to day as a normal user, but when I switch to power user mode its... It makes maintaining my system very unenjoyable.
For me personally systemd is much better especially for services and logs. It creates a consistent environment and provides lots of features like sandboxing and failure detection. I really don't like how some software dumps random logs everywhere and having a proper database is nice. Journalctl is tricky to learn but it is nicer than trying to manage text files.
We literally have /var/log/ as a well-known standard though. Almost every piece of linux-standard software dumps to a subfolder by the app name in there. Systemd should at the very least have the capability to mirror there so you can get at the logs in a sane way.
I can't say I agree but I see where you are coming from.