On Fri, 8 Nov 2019 11:29:09 +0100, "R.Wieser" 
declaimed the following:

>
>I wanted to add a shell script to init.d, and and had a ball with googeling
>enough info to be able to successfully add a script to the boot sequence.
>:-\
>

 Sys-V init.d is, to my knowledge, being deprecated in Debian based
systems. It is being replaced with systemd (and even more cryptic scheme,
in my mind) -- though the link (below) implies some of it is still in use.

>
>For instance, there is a "Default-Start:" line followed by a number of
>digits and sometimes an "s" too.   No idea what they mean, or why there are
>multiple present.
>

>
>So, does anyone know of a decent description of that init.d files header ?
>Possibly an example/template file too ? :-)
>

 The common init.d scheme is to have one directory with a pair of files
for each feature. The file will have an S or K (start/kill), some name with
a few digits to provide a priority..

 Then, in the various run-level directories, there will be sym-links to
the real files. When an init.d system changes run-level, it runs the k*
files for the current level, then runs the s* files for the level it is
transitioning into..

https://wiki.debian.org/RunLevel
https://www.debian.org/doc/manuals/debian-reference/ch03.en.html#_stage_4_the_n
ormal_debian_system
"""
systemd offers backward compatibility features. SysV-style boot scripts in
"/etc/init.d/rc[0123456S].d/[KS]" are still parsed and telinit(8) is
translated into systemd unit activation requests.
"""
 Further down it mentions that Sys-V run levels 2-4 all result in the
same systemd "target" (run level 5 maps to the graphical display target)


--
 Wulfraed                 Dennis Lee Bieber         AF6VN
 wlfraed@ix.netcom.com    http://wlfraed.microdiversity.freeddns.org/

--- SoupGate-Win32 v1.05