this post was submitted on 26 Jan 2025
351 points (94.0% liked)
memes
11276 readers
3431 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to [email protected]
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- [email protected] : Star Trek memes, chat and shitposts
- [email protected] : Lemmy Shitposts, anything and everything goes.
- [email protected] : Linux themed memes
- [email protected] : for those who love comic stories.
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
Ok so I'm just my own system administrator, yet I like systemd because I remember how much less... reliable the former alternatives were on my computers.
BUT. I dislike having to learn more commands just to read my logs, and systemd timers are awfully complicated when I just needed what cronjobs already did.
I manage what people call Large Enterprise. As my side gig, I manage Small Offices / Branch Offices.
Remember that systemd is also used on massive server farms that need consistent fast reboots during recovery from vary occasional mishap. These things have all but a stopwatch running.
My god, is systemd ever a piece of crap. Coupled with 'consistent[ha!] naming' it's the single most likely thing to cause a field engineer to scream into the partially-lit datacenter in abject rage and hate. Even more if they remember how fucking sysVinit actually delivered on the promise. Even more if they still remember how well inittab Just Worked.
I read starry-eyed lennartophiles praising the reliability and ease of use and I wonder whether they didn't know the basics of systemd, or just don't understand the problems plaguing servers now. Like apple fans, screeching at non-apple users, I worry this lack of understanding causes a very biased approach where issues with apple/systemd are "just impossible to solve" where android/runit issues are "obvious indications why they're broken systems and should be avoided; and also you're old if you like them."
You signed up for this.
You signed up for this.
It's like those shitty cable bundles where you want HBO Max but also have to buy 4 channels of Golf, 2 of only Nascar-based Reality shows, and one that just shows Real World marathons, over and over; and also have to pay for all 8 .
THE UNIX PHILOSOPHY is to not over-reach the designed purpose. It allows for combinations of tools based on what's more reliable/current/compatible at the current moment and keeps tools concise. Having things move over to timers from cron or xkcd/927 logging because Lennart and Kay couldn't be bothered to understand and work with what's existing, and deciding to replace everything by this growing blob of monolithic dreck, is bad for a reason that's been proved in the past. And those who are too lazy to read history will elect fascists. or something.
I'm an older fella who supported BSD systems before transitioning careers, the damn fact that you can't just read a log file by default was enough to get my hairs up. I like using other simple tools to handle parsing for important info or events as well.
I still subscribe to the philosophy as you put it, a system is only as reliable as it's components.. the sum of simple tools worked way better than systemd ever has in my opinion.
As a developer who got into DevOps and now is learning the vast world of sysadmin stuff, it’s validating to see you say that. Because the damn logging system is my number 1 gripe as well and it discourages me from doing any real digging. Why would I when I can just spin up a new VM?