These days the information in the LSB header is used.

Manually specifying/overriding runlevels as a parameter to
update-rc.d on command line is even deprecated and a noop stub
these days.
---
 policy.sgml | 13 -------------
 1 file changed, 13 deletions(-)

diff --git a/policy.sgml b/policy.sgml
index 07b7e4f..32e1efc 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -7691,19 +7691,6 @@ test -f <var>program-executed-later-in-script</var> || 
exit 0
            </p>
 
            <p>
-             By default <prgn>update-rc.d</prgn> will start services in
-             each of the multi-user state runlevels (2, 3, 4, and 5)
-             and stop them in the halt runlevel (0), the single-user
-             runlevel (1) and the reboot runlevel (6).  The system
-             administrator will have the opportunity to customize
-             runlevels by simply adding, moving, or removing the
-             symbolic links in <file>/etc/rc<var>n</var>.d</file> if
-             symbolic links are being used, or by modifying
-             <file>/etc/runlevel.conf</file> if the <tt>file-rc</tt> method
-             is being used.
-           </p>
-
-           <p>
              To get the default behavior for your package, put in your
              <prgn>postinst</prgn> script
              <example compact="compact">
-- 
2.10.2

Reply via email to