Quoting Joerg Mayer <jmayer@loplof.de>:
With all that discussion going on and mentioning that "even Debian" is going towards systemd, has anyone looked at one of their ideas to only maintain systemd config files while maintaining systemv-init for those who feel they want/have to keep it? http://www.h-online.com/open/news/item/Debian-testing-a-systemd-to-sysvinit-... Would an approach like this make sense for an interim period instead of dropping systemv-init "too early"? I don't think the approach will work for the core boot stuff, but for normal packages, it looks like a good compromise: Only maintain the systemd config files and generate systemv-init files from them at install time.
Plugging in LSB init scripts has (to my knowledge) always been part of Systemd support. One of the main problems in openSUSE is that we ship in a lot of packages two 'startup command' templates, one for each. If the name is equal, then the 'systemd' variant will simply overload the sysv (which works as expected), but you have more complex cases (thinkg for example /etc/init.d/network vs the various things systemd does, as it for example knows about NetworkManager or other implementations). There a pure overload does not reliably work (ok, it does now.. thanks to the work done by the devs for this special case I guess). 3rd party vendor init scripts are not really an option to be ditched in the short term... no way around this. Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org