|
Authored by: Wol on Saturday, July 28 2012 @ 11:03 AM EDT |
Well, the reason is, if you read the systemd documentation, that SysV init
scripts are a huge pile of spaghetti.
In MAJOR breach of the Unix "do one thing and do it well" philosophy.
Systemd takes all the things that are repeated time and time again in any
well-formed SysV script, and replaces them with little executables.
I'm not going to comment how well (or not) systemd has achieved its aim, but the
intention is to make things much simpler. Instead of 90% of a SysV script being
a copy of other SysV scripts, it's now a call to a shared routine. Much less
opportunity for bugs. Much less live code for bugs to hide in. And most scripts
- containing thousands of lines of boilerplate - replaced by a config file maybe
ten lines long.
Oh - and systemd sets out to be SysV compatible. It's just that, rather than
putting systemd in a SysV wrapper, it does it the other way round putting SysV
in a systemd wrapper. And if that doesn't work, it's a recognised systemd bug
(unless they find the bug in the SysV script! :-)
Cheers,
Wol[ Reply to This | Parent | # ]
|
|
|
|
|