this post was submitted on 26 Feb 2025
196 points (77.4% liked)
linuxmemes
22926 readers
1777 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.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
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. Even if you watch it on a Linux machine.
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. Β
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
I still don't know what people use to create services other than systemd
If you're writing bash scripts you're basically replicating a lot of the functionality of systemd but with larger foot guns
The system V init approach did the job fine for a couple of decadesβeven if the actual service definitions were a glorified shell switch statement as you insinuate.
Canonical did their upstart thing for a couple of years that wasn't too bad to use, personally I'm glad they ended up switching to systemd though.
Abaci and mechanical differentiators did the job just fine for a couple centuries.
Just go back to rocks on a scale we'll be fine
s6, dinit, openrc, BSD rc, are all alternative init systems with their own method of doing thing
Guix_SD has its own init system, Gnu shepherd
All of them are worse in my experience. In a embedded context I use busybox init and if I need something more I used systemd. Systemd actually has a fairly small footprint. A few years ago I ran it on a system with 32mb of ram.
In my experience s6 was considerably faster and less verbose and didn't have systemd's garbage design, but it was considerably more difficult to understand and use
dinit is apparently easy to use, but I haven't used it
We can use dinit, s6, runit, and openrc.
There are more, but these are all top contenders.
I switched to dinit recently, it uses declarative service management (like systemd unit files). Very clean, fast, lightweight, and portable.
You have that backwards
If you're writing Systemd profile profile profiles you're replicating shell scripts but with a lot of spongey unknown "come on, pumpkin" cancer code that you're only sure will do what you think because you don't know what suddenly capriciously changed in enterfuckingprize code and boy is your remote server screwed. Fuck me if I need to actually rely on something starting.
No one said sysV is awesome. It's built to best practice and it does what it does really well, but that's not a lot. But it does it well. Oh, the days Systemd has ruined trying to work half as well as ; well fuck, every alternative.
The days Systemd doesn't ruin, it's the other cancer, network manager and 'consistent' naming. And devices that don't come up. And devices that don't actually assign a fucking static goddamned address. #youHadOneJob
Spot the parts of enterprise Linux that runs like shit and barely does the same thing twice on two identical adjacent boxes, and I'll show you some whiz kid who shat out some cancer and went to go work at Microsoft.
So. Anyway, because the reliable stuff came before Systemd's change-for-lulz setup, you had them in the wrong order unless you have a time machine.
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.
journalctlis 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.
Very much this, why is systemd entangling itself in every part of the linux kernel, I ripped that mfer network-manager and installed iwd
I'm on guix-sd and don't have to suffer systemd
Amen.