Comment 3VA sysvinit was a dead end

Story

Linux kernel hacker's open rant about systemd

Preview

sysvinit was a dead end (Score: 4, Insightful)

by mth@pipedot.org on 2014-08-14 00:53 (#3VA)

I'm not a big fan of systemd, but I disagree with the idea that sysvinit didn't need replacement.

It required a large amount of boilerplate in the service start/stop script, which was different between distros, making it a lot of work to provide a decent start/stop script for your daemon. The hard work of distro maintainers hid this nuisance from most end users though.

Ordering the service startup sequence by manually assigning priorities to them (S80myservice) instead of using dependencies is a terrible hack. It also prevents services from being started in parallel, which is a pity on today's multi-core systems. It's like building your code using a shell script instead of a Makefile.

There is no consistency in how services are started: inittab can respawn, init.d scripts can query the service status (on some distros!), (x)inetd can start services on demand, but all have different configurations.

I have some doubts systemd is the right solution to these problems, but at least there is movement now. In my opinion, the solution would be to improve systemd or replace it with something better, not going back to sysvinit.

Moderation

Time Reason Points Voter
2014-08-14 03:09 Insightful +1 bryan@pipedot.org
2014-08-14 03:59 Insightful +1 fishybell@pipedot.org
2014-08-14 14:09 Insightful +1 vanderhoth@pipedot.org

Junk Status

Not marked as junk