Thomas Goirand <z...@debian.org> writes: > On 02/19/2014 08:05 AM, Henrique de Moraes Holschuh wrote: >> On Tue, 18 Feb 2014, Russ Allbery wrote:
>>> There are some advantages to providing only one version with knowledge >>> of all of the init systems given that we're supporting init system >>> switching, and therefore may need to set up state for init systems >>> that aren't currently running so that switching can work properly. A >>> good example is registering an init script with insserv so that the >>> correct S and K links are created even if the system is currently >>> booted with a different init system. >> I agree. > I agree as well, but it's simply not what is currently being done. > Currently, sysv-rc & OpenRC both provide update-rc.d and invoke-rc.d. If > we could move them to sysvinit-utils, why not. It'd be also nice to have > invoke-rc.d write the symlinks in /run/openrc/started no mater what, so > that OpenRC could know how to shutdown quickly after switching init > system. Note that I already patched the "service" tool for this, but it > will only do something if /run/openrc/started exists as a folder. > Suggestions welcome. If it improves integration with OpenRC, I'm in favor of modifying the current invoke-rc.d to support this. I think moving update-rc.d and invoke-rc.d to a generic package and using them across all of our supported init systems makes the most sense. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87bny38sw1....@windlord.stanford.edu