Didier Kryn <kryn@???> writes:

[...]

>     A few releases ago, intoducing a new init script in /etc/init.d,
> and the corresponding links in rc?.d has become a little more
> complicated, because the comments at the head of the script now
> consitute a meta-language describing the interdependencies of these
> scripts. AFAIR, after copying the script in /etc/init.d, the admin
> should invoke update-rc.d in some way to do the job.

update-rc.d (which used to be the tool for creating a set of 'default'
start/stop links) has been extended to deal with the other situation,
too, but provided an init.d script contains a valid set of 'LSB
headers', eg, from /etc/init.d/udev,

### BEGIN INIT INFO
# Provides:          udev
# Required-Start:    mountkernfs 
# Required-Stop:     
# Default-Start:     S
# Default-Stop:
# Short-Description: Start udevd, populate /dev and load drivers.
### END INIT INFO

(maybe useful as a template here)

the real 'installation program' is called insserv (originally came from
SuSE Linux and was a server at some point in time in the past). In order
to install a script, it can be invoked as

insserv </path/to/script>

(insserv -r removes a script).