●Stories
●Firehose
●All
●Popular
●Polls
●Software
●Thought Leadership
Submit
●
Login
●or
●
Sign up
●Topics:
●Devices
●Build
●Entertainment
●Technology
●Open Source
●Science
●YRO
●Follow us:
●RSS
●Facebook
●LinkedIn
●Twitter
●
Youtube
●
Mastodon
●Bluesky
Catch up on stories from the past week (and beyond) at the Slashdot story archive
Forgot your password?
Close
Post
Load All Comments
Full
Abbreviated
Hidden
/Sea
Score:
5
4
3
2
1
0
-1
More
| Reply
Login
Forgot your password?
Close
Close
Log In/Create an Account
●
All
●
Insightful
●
Informative
●
Interesting
●
Funny
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
bydrinkypoo ( 153816 ) writes:
Poettering will also continue to remain deeply involved in the systemd ecosystem.
I therefore trust that it will continue to be shit.
bytwinirondrives ( 10502753 ) writes:
for people hacking together their own systems I'd admit that systemd does nothing for that. But organizational level mass deployed systems are pretty much barred from linux without something filling that role. then I think systemd was an idea put forward around the same time io_uring was which maybe possibly was the beginning of a compliant solution filling the systemd role. my opinion is io_uring actually increased the attack surface of linux systems. would that have been different if systemd never existe
byShaitan ( 22585 ) writes:
Overrated. Prior to systemd Linux administrators famously admin'd thousands of systems vs tens in the windows world. That text/file/directory-based system combined with all the text-mangling power tools in linux, the shell, and perl... nothing compares.
It actually becomes much easier to work with configuration management tools when they are managing the state of text files as the Linux gods intended.
bydskoll ( 99328 ) writes:
Systemd units are plain text files, you know.
I honestly don't understand the visceral hate for systemd. I've been using UNIX since 1989 and Linux since 1994, so I have plenty of experience with old ways of doing things.
Systemd, at least in my experience, just works and writing systemd unit files is easier than writing sysvinit scripts. So when Debian switched to it, it was fine. I adapted.
bydrinkypoo ( 153816 ) writes:
I honestly don't understand the visceral hate for systemd.
It is the antithesis of the Unix way. This has been argued back and forth all along, and if you don't agree I won't try to convince you here.
Systemd, at least in my experience, just works and writing systemd unit files is easier than writing sysvinit scripts. So when Debian switched to it, it was fine. I adapted.
The problem with systemd and unit scripts is that they cannot do all the things that a script can do, so you often wind up using a script anyway. In that case you have really not made things any simpler than the usual case. Meanwhile you've added a whole lot of complexity which is largely unnecessary, some of which is utterly dependent on other parts so it is difficult
byShaitan ( 22585 ) writes:
You: "you often wind up using a script anyway. In that case you have really not made things any simpler than the usual case. Meanwhile you've added a whole lot of complexity which is largely unnecessary"
Him: "Systemd, at least in my experience, just works and writing systemd unit files is easier... I would say: very rarely, not often."
If this isn't a constant repeat of Unix philosophy clashes with Microsoft monolithic one-size-fits-all solution then I don't know what is. Yes it is easier to walk up and configure the monolith if you fit the use cases it addresses, often MUCH easier, yes it addresses the majority of use cases. The learning curve is much lower.
But once you overcome the learning curve the flexible combination of single purpose tools is MUCH more powerful and lets you handle cases the one-size-fits-all solution can't solve at all. Also there are ways to script/template or otherwise automate out those common use cases.
Reply to This Parent
twitter
facebook
Flag as Inappropriate
bydskoll ( 99328 ) writes:
But you are not making sense. (And it's "Her", by the way, not "Him".)
As the person I replied to pointed out, if systemd doesn't quite do what you need, you can always fall back on a script. So the common use cases are easy and the uncommon ones are possible.
Now I personally have not encountered a use case that systemd couldn't handle natively, but I'm willing to admit that such use cases exist, in which case... you use a script that you call from a systemd unit. Problem solved.
bydskoll ( 99328 ) writes:
OMG, lookit the triggered snowflake! LOL. A whole paragraph to whine about a simple two-letter spelling correction.
byBarsteward ( 969998 ) writes:
Misogynist alert !!!
● current threshold.
There may be more comments in this discussion. Without JavaScript enabled, you might want to turn on Classic Discussion System in your preferences instead.
Slashdot
●
●
Submit Story
It is much harder to find a job than to keep one.
●FAQ
●Story Archive
●Hall of Fame
●Advertising
●Terms
●Privacy Statement
●About
●Feedback
●Mobile View
●Blog
Do Not Sell or Share My Personal Information
Copyright © 2026 Slashdot Media. All Rights Reserved.
×
Close
Working...
Working...