On Monday 14 of November 2011, Stefan Seyfried wrote:
You would need to touch each and every init script.
I don't think so. A simple change to /etc/init.d/rc (and /etc/init.d/boot if you want the same for boot.* scripts) would be enough.
I forgot a few more benefits:
* lossless loging from the beginning * easy display of system state (stuff like systemctl list-units --failed - do this with sysv init!) On real work systems, nobody cares what's printed on the console - simply because there is no console attached. But people care how to find out if startup worked. And they care for logs.
Again, these things either are already done for traditional init scripts or can be done easily.
(Sys V init mysteriously (and no way to find out why!) not starting single init scripts even though the S* and K* links were there is just one example).
This is a nice example of problems that are easy to debug with traditional init scripts but much harder with systemd.
So instead of complaining I decided to simply fix the stuff that's still causing troubles. But for now it is just working fine for me and I will have to find something to fix.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org