Richard Brown wrote:
On 9 April 2014 18:28, Roman Drahtmueller <draht@suse.de> wrote:
Having an init script and not needing it is better than needing it and not having it. Apparently, it doesn't harm, but rather helps.
I disagree - having both the systemd service file and the /etc/init.d file present on an installed machine causes confusion, both at a system level (eg. different answers to /etc/init.d/SuSEfirewall2 status and systemctl status SuSEfirewall) and at a sysadmin level ("What command do I use to do X?" - we don't want to have 2 different commands with 2 different results serving the same purpose)
Then get rid of the systemd interface -- it is confusing. No new commands for everyone to learn, no new "everything is different" problems -- I noted that even samba was recently called out for not being compatible with systemd's "quirks" and requirements -- of course the fact that it's been a working project for 15+ years is inconsequential. All must adapted to the new dominator.... *blech*.
I agree with the argument that having the sysVinit script is good for non-systemd build targets, but for openSUSE 13.2 and beyond we use systemd, and in our distro, we should only be using systemd unit files
Why? Because you will feel uncomfortable and insecure if anyone is still running sysVinit on their 13.2 system? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org