3 ms·
First, it's less complex because the technology involved (shell scripts) are simpler to learn, design, implement, customize, debug, etc. Second, it's less compl
by peterwwillis 13y ago
First, it's less complex because the technology involved (shell scripts) are simpler to learn, design, implement, customize, debug, etc. Second, it's less complex because it's based on known technology and there's no learning curve. Third, it's less complex because the components it depends on are independent and small/simple, versus monolithic and interdependent. Fourth, troubleshooting sysvinit is incredibly simple, and you don't have to know anything about the tools involved to debug them. Fifth, it's less complex because there's less specialized operation to take account of.
Keeping track of child processes does not mean that the system is under control, nor that I understand it better, which is necessary for me to have control. And cgroups are not necessary at all to manage child processes. They simply make it more compartmentalized, and help deal with zombie parents, which also can be dealt with without cgroups.
So your language has to have D-Bus bindings, which hopefully are maintained for your language. And you have to learn how to use those bindings. More complex, more things going on under the hood, steeper learning curve.
The features I refer to are site-specific. I've worked for many companies that heavily modify their services and system init, logging, etc to fit their needs. I've worked on embedded applications, big server farms, and custom tailored products. They all customize various parts of the operating system, and have written custom features for them. Now it all has to be rewritten for systemd.
I can't comment on the exact decision-making process behind adopting systemd, but I can say almost all of what I have read about it is based on a mob mentality that tries to impose its will on the organization rather than work out compromises.
- whatevsbro 13y agoFLAWLESS VICTORY (Yeah yeah, Reddit, I know.)