While this is in fact not the prettiest solution, and makes it a little harder to find out how this works. On the other hand, as I see it, this mechanism exists only for backward compatibility reasons, and actually provides an elegant way to allow the software packager to provide both SysVInit scripts and systemd units, which can be used with either init daemon without change (so actually, there's no need to touch existing and working SysVInit scripts at all). However, if systemd is being used as the init daemon, systemd will be used to start the service.
Yep.
there was a time that init did just fine by looking up the names of the links under /etc/rc.d/rc.x and started them in order and killed them in order. That would be a good method to go back to. Ruben -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org