On 28 May 2015 at 12:31, Lennart Poettering <lenn...@poettering.net> wrote: > On Wed, 27.05.15 15:13, Martin Pitt (martin.p...@ubuntu.com) wrote: > >> Hello, >> >> if you have both a systemd unit and a SysV init script with the same >> name, systemctl {en,dis}able currently diverts to chkconfig and >> friends *only*, without actually enabling/disabling the native unit. >> This is a non-issue for Fedora packages which eliminated init.d >> scripts, but still an issue for e. g. Debian or third-party packages >> which want to support multiple init systems. > > Hmm? THis sounds the wrong way round. What currently happens should be > this: if both are available systemd ignores the sysv script, and only > considers the native unit. Is that what you are trying to say? > > And you now want everything to be applied to both the sysv script and > the native unit? > > What happens if we query the state of things with is-enabled, then?
Debian supports rebooting with either sysv-init or systemd.... hence the key point here multiple init systems, simultaneously within single install. -- Regards, Dimitri. Pura Vida! https://clearlinux.org Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel