Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
I exhaled from my nose, but at the end this joke doesn't seem fair.
I've been running Artix for years, because I wanted to try it out for fun and now am too lazy to switch, cause most things just work. I update weekly just fine and sometimes I have to write an init file for openrc.
The biggest pain point was when I was trying to debug an issue which crashed KDE and realised that there is no journalctl ofc.
Like with most technology, init should be based on use-case.
Some setups are not made for quick reboots and that’s ok. When all your container does is run ddclient you might find that even cron can work just as well as systemd.timers
For me, even using Linux at all is more of a philosophical decision than a practical one.
As long as the tradeoff is not too big, I'd rather use what follows my values over going by pure meritocracy.
Same for me, missing on some debugging advice on the internet but for the most part is fine!
I'm not a linux power user but have some servers running on linux and honestly wouldn't change it with anything else, as everything runs smooth and maintainance is easy and straight forward. Even if something gets fucked there is a great online community which helped me out everytime.
That said, and sorry for the long introduction:
I read a lot systemd memes in the last weeks: What is the problem with it and why is it trending now?
Nothing new. Nothing recent. Just people being scared of something because they don't know how it works or because it's relatively new.
Major distros have started adopting it in recent years. It's one of many ways for a distro to manage which services are running. Many of the others are essentially a hodgepodge of shell scripts.
systemd provides a lot of flexibility with service dependencies and logging, amount other things. It has a standard way to have user-scoped services. It's standardizes filtering logs for specific services.
Barely recent years at this point, Ubuntu switched in 2015!
basicly people complaining about what they don't understand, that it don't follow unix philosophy, when that philosophy was created 50 years ago, any way,etc, if systemd wasn't good anyone could have adopted it, and everyone did, beause it easier, it's faster and it work
https://youtu.be/o_AIw9bGogo?si=83QbNSQgG646M98_
good video about it
I'm neither a systemd fan nor a hater, but in my experience not even enterprise linux distributors can get it to work correctly all the time. That tells me that maybe it is too complicated.
Here is an alternative Piped link(s):
https://piped.video/o_AIw9bGogo?si=83QbNSQgG646M98
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source; check me out at GitHub.
Sysinit was basically one file where you tell a process what to do, start, reload, stop. Systems is way way more complicated and according to some, prone to breaking.
It's funny, after your first sentence, I thought “yeah, that's exactly the problem. Copy&paste fragile shell code for managing processes instead of standardized lifecycle management”. Then your second sentence painted that horrible mess as “less complicated”
Thanks, and understood. Do you also know why this topic is trending right now? Systemd isn't some brand new thing, so why the sudden outcry?
It's been hated since day 1, perhaps only now are you starting to see and understand what people say about it.
That could be it.
I feel like this is a Slackware joke
Nah, if it were slackware there'd be more Bob.
Tmux over gnu screen? Too progressive for me!
I was really hoping this would be American Sign Language linux. All you’d need to do is develop a writing system with hand shape, face shape, location, and motion characters then build an entire operating system around it…
Don't forget the different syntax. When, where, actions.
It's all fun and games until you can't even reboot cleanly because systemd isn't responding...
Idk what you did, but I never had a problem where systemd isn't responding, and I've been running Linux since I was a teenager.
Shoot, if running a ceremonial kshell script every Friday evening makes me a ludite, I'll be shouting angrily at the cloud any day now.
/s, obviously, beacuse I already yell angrily at the cloud.
Office suite "vim and mutt" Every thing else is bloat.
Joke's on them, I use emacs as an OS.
I need to edit text files over SSH tho, haven't been able to find a good text editor...
Gotta admit, I'm impressed. You've actually made me want to defend the anti-systemd crowd. Just take the W, you don't have to rub it in.
Keep your hands off my network-scripts