Bug#225465: debian-policy: packages must give choice to not start at boot, via debconf

[Thomas Hood <jdthood@yahoo.co.uk>]

[resent]

> Debian should no longer be like some mere arcade kiddie game machine,
> where if you don't like the games staring when you deposit your coin,
> then sorry.

The System V init system has its limitations.  Nevertheless I am
opposed to any scheme that would introduce a new layer of runlevel
configuration on top of the rc symlink farms.  Indeed, I would rather
hear policy dictate that there be _no_ such layer.  If the admin
does:

    /etc/init.d/foo start

or even:

    /etc/rc2.d/S20foo start

then foo should start.  Period.

The correct way to disable the starting of a service in a particular
runlevel is to change its "S" rc symlink for that runlevel to a "K"
symlink.

The only problem with this is the loss of information it entails.
Once the admin has renamed the symlink, unless he keeps a record of
his action, he won't know to what name he should rename the symlink
back if he chooses to re-enable the service.

This problem can be solved with a higher level administration tool.
It need not and should not be solved by adding complexity to the
System V init system proper.

Josip Rodin <joy@srce.hr> wrote:
> That's one debconf question too many. The instructions for stopping
> the starting of daemons are pretty simple -- for the vast majority of
> users it's simply a matter of
> 	rm /etc/rc2.d/S??daemonname

No, it is a matter of:

        mv /etc/rc2.d/S20daemonname /etc/rc2.d/K80daemonname

The reasons:
* If you remove all rc symlinks then the package may reinstall them
  on upgrade.
* The behavior of the init system is not defined if there is no
  symlink for the service.

This point aside, I agree entirely with Henrique de Moraes Holschuh's
posting, message ID 20031230121818.GD4010@khazad-dum.debian.net.

-- 
Thomas Hood <jdthood@yahoo.co.uk>