Hi, We are now using systemd for a very long time, and there should be no reason anymore that anything depends on SysV init support. aaa_base still ships some of this leftovers: * /sbin/service * /usr/libexec/initscripts * /usr/libexec/initscripts/legacy-actions There is only one legacy package using /usr/libexec/initscripts, and this is "ntp". A SR to remove that is pending for over three weeks now. So since nothing is using that anymore, I would like to remove support for it from aaa_base. /sbin/service is used by rc* symlinks by us. Is there anything else calling /sbin/service? /sbin/service is a complicated shell script, which tries to find out if a systemd service should be managed or a SysV init script. But we don't have SysV init scripts anymore and the remaining support will be removed upstream short or midterm. So most of the complex code can be safely removed. Remains the rc* symlinks. For what are they good? The only benefit is, that a user does not need to bother if this is a SysV init service or a systemd service. We don't have SysV init scripts anymore. So in the end it's always calling systemctl. Many systemd services don't have a rc* symlink, so people have to learn to use systemctl anyways. No other Linux distribution seems to have rc* symlinks, so they are not needed for compatibility. My proposal: * remove SysV init support from /sbin/service and add a deprecated notice * remove rc* symlinks * drop /sbin/service Regards, Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nuernberg, Germany Managing Director: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)