Per Jessen wrote:
Andrei Borzenkov wrote:
On Tue, Apr 26, 2016 at 9:16 AM, Per Jessen <per@computer.org> wrote:
If anything, systemd-sysv-convert should be invoked automagically, but
Package has to call it manually (it is done via macros, but these macros must be explicitly included in spec). And those macros are expanded when package is created, so unless it was built for (open)SUSE and using (open)SUSE macros, this tool won't be called.
What happens when it isn't called? I often install the HP Proliant Support Pack which is not specifically openSUSE "compliant", but it works perfectly fine. It has 2-3 init scripts.
Ditto for the 3ware array management daemon, also works fine. I have to deal with LSB init scripts for quite some time to come. Manufacturers (in my case HP, IBM, 3ware) do not upgrade or fix their software packages. You want an update, you buy a new card or a new box. Even then there's often no (open)SUSE-specific support.
I'm not intimately famniliar with the process. To my knowledge there is no conversion "needed", LSB init scripts are supported as they are.
Yes, but you may need to use old insserv/chkconfig tool in this case, I am not sure if systemctl enable/disable still supports legacy scripts.
I think it does, but I haven't tried it for a while.
Just tested it on Leap421 - stork2:~ # systemctl disable tdm2 tdm2.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig tdm2 off stork2:~ # systemctl enable tdm2 tdm2.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig tdm2 on -- Per Jessen, Zürich (8.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org