News for hackers. Stuff that matters.
Re:Why systemd is still divisive after all these years by m463 on Friday June 19, 2020 @04:55AM (#23572559)
I think at this point, the systemd mess is an opportunity.

Write a better one.

"Be the change that you wish to see in the world."- Gandhi (maybe)

Re:Why systemd is still divisive after all these years by dTal on Friday June 19, 2020 @06:28AM (#23573018)
There are already better ones. The problem is more social than technical. I'm using Void Linux with runit and it's simple and functional; I've never once missed systemd. And the BSDs all manage fine without it as well.
Re:Why systemd is still divisive after all these years by vlovich123 on Friday June 19, 2020 @03:34PM (#23578087)
> runit employs a concept of a service directory, responsible for an individual service, which is a process to monitor and an optional log service

Hey look at that. The critique that systemd has a log daemon (why does init need a log daemon?) doesn't really fly. Also runit doesn't have the ability as I understand it to properly specify dependencies between components falling back to the crap of runlevels. You won't see it as a user. You see it consistently & repeatedly as an OS developer/maintainer & through slow boot times. Then you have upstart which has some dependency & parallelization effort.

The fundamental architectural flip that systemd takes is, as I understand it, that each service/process starts as needed & just blocks on I/O letting the kernel manage parallelism implicitly through synchronization mechanisms that are robust & easy to maintain rather than manual config files. There's a lot of complexity here. There's name discovery & registration so that when you have a dependency on you, you automatically start whenever a dependency tries to access you. The logging mechanism is because you want to make sure that logging is robust & functional. The binary mechanism is great because it drastically shrinks the size of the log files, reduces the overhead (printf format strings are expensive), & makes it easier to write tools to process them.

I'm not sure about the DNS & other binaries but I'm sure there are similar intrinsic architectural problems those tools are solving. Again, none of these are necessarily ones you see as an end user directly. You see it indirectly because a lot of diffuse time is spent finding/fixing bugs due that architecture (yes there are still bugs but they're of a different flavor, and, hopefully, bugs you'd have in either system.

BTW when I last looked at systemd, superficially it looked very very similar to launchctl in terms of design with many of the same benefits.

Re:Why systemd is still divisive after all these years by zozbot234 on Friday June 19, 2020 @07:04AM (#23573164)
It's not that trivial to "write a better one" while broadly keeping the behavior and desirable features that systemd proponents have come to want. It will have to happen at some point, because the sheer amount of incidental complexity in systemd is quite unsustainable - but a lot of hard, fundamental work will be necessary.