On Wed, 9 Apr 2014 22:53, Richard Brown <RBrownCCB@...> 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)
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
Don't we have some nice macros that give us systemd unit files for some build targets and includes sysVinit files for others? if not..maybe that's an approach we can take.
A suggestion for factory (13.2) and the upcomming SLE 12: put the sysVinit scripts in %doc, at least for the next release. That would remove them from /etc/init.d/ but preserving them for easy access if needed because the original script had features that aren't realised for systemctl / service yet. See post about scriptlets for that (was somewhere in the last four weeks on this list, I believe) - Yamaban. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org