It's not modular, it's a mess. Systemd may be organized into separte components, but make no mistake - it's a monolith in sheep's clothing.
As for unit files, nosh, at least, provides the same format as systemd. s6 "unit files" are just the command to daemonize the process, in most cases. BSDinit and OpenRC are pretty simple as well.
>Then go and use UNIX, aka BSD. This is the linux world, and most people want it – as seen in the countless times when distro maintainers held a vote pro or con systemd.
Linux is a UNIX too, and most of the people who know and care about init systems don't want it, judging by the massive protests that show up constantly from people who understand the technical aspects.
>Again, the entire point is that it just works and is still easily configurable and modularized.
It "just works," but it's a technically deficient mess that goes against everything unix is about, is a monolithic beast in disguise, and is trying to force everyone to use it.
If it weren't for that last bit, I really wouldn't care.
>Systemd is to sysvinit what Linux was to Hurd and other microkernels
That's just not true. Linux was a return to a simple, tried-and-true model from a more complicated and theoretically beneficial one. Systemd is a devergance from a simple, tried-and-true model to a more complicated one, that really doesn't have many benefits.
>And "s6 "unit files" are just the command to daemonize the process, in most cases" is a horrible solution, too.
>The reason systemd unit files are so awesome is because they’re simple configuration, not having to string complicated commands together.
So are S6 unit files. So are a lot of config formats, actually. Sysvinit was really bad, but other inits had moved on. The complicated commands are only required when the app had complex requirements, or when init is stuck using fragile pid handling, which S6 and the like don't need, because they implement proper process monitoring.
>You fundamentalists had 2 decades to make a working system
BSDinit, OpenRC, s6, hell, even upstart, and countless others are all working systems.
Anyways, I'm not a fundamentalist. I don't think that systemd's unit files are broken. What I think IS broken is systemd itself.
Init has a few jobs: managing startup, managing shutdown, reaping processes, and handling daemons, etc. By this point, init's job is well defined. How it should do them has been argued, but the jobs are well defined. That is what init should do. NOTHING ELSE.
Systemd tries to do everything. Thus, it's overly complex, AND it's a single point of failure.
>It’s time to end this.
I quite agree: When Lennart stops making me try to use his piece of trash disguised as software, I'll stop complaining about it.
As for unit files, nosh, at least, provides the same format as systemd. s6 "unit files" are just the command to daemonize the process, in most cases. BSDinit and OpenRC are pretty simple as well.
>Then go and use UNIX, aka BSD. This is the linux world, and most people want it – as seen in the countless times when distro maintainers held a vote pro or con systemd.
Linux is a UNIX too, and most of the people who know and care about init systems don't want it, judging by the massive protests that show up constantly from people who understand the technical aspects.
>Again, the entire point is that it just works and is still easily configurable and modularized.
It "just works," but it's a technically deficient mess that goes against everything unix is about, is a monolithic beast in disguise, and is trying to force everyone to use it.
If it weren't for that last bit, I really wouldn't care.