[Pkg-sysvinit-devel] Bug #826214: Bug #826215: init-d-script and systemd: solution

Martin Pitt mpitt at debian.org
Sun Dec 25 20:18:44 UTC 2016


Hello Christian,

Christian Seiler [2016-12-25 13:34 +0100]:
> I think I have a solution to both issues - and my solution
> does not require any change to any individual init script,
> and best of all it doesn't even require changes to any
> sysvinit-related package (we get to have our cake and eat
> it too):

Thanks for working on this!

> The systemd package could install a diversion of /lib/init/init-d-script and
> install its own wrapper.

I don't like this approach, to be honest. (1) This diversion would be present
on practically all installs anyway, as it would (necessarily) be in the
"systemd" binary, not the "systemd-sysv" one. (2) I don't want to maintain this
SysV stuff in the systemd package forever, AND still have someone else maintain
the non-diverted variant in sysvinit-utils. I'd much prefer to just change the
"master" copy in sysvinit-utils, and packages which use that should grow a
dependency to that (so that it can become non-essential).

I. e. use your script but patch the current one instead of duplicating it.
If the SysV init maintainers don't want to carry this either, then there's
still the option to just drop the systemd integration, and break calling
/etc/init.d/foo directly under systemd. WDYT?

Thanks,

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)



More information about the Pkg-sysvinit-devel mailing list