Canonical method to locally disable an init script?

Thorsten Glaser t.glaser at
Tue Nov 24 16:33:27 GMT 2020

On Tue, 24 Nov 2020, Bob Proulx wrote:

> Here is an example to help clarify:
> In order for local changes to persist at least one symlink must be
> present so that the installation tools know that this is previously
> exist and that they should not install the default.

Ah, thanks, that makes sense.

So using disable is correct, defaults-disabled and remove isn’t,
and the update-rc.d manpage probably could use this piece of
information, and insserv should not warn if all symlinks are K,

15:41⎜<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)

More information about the Debian-init-diversity mailing list