> On Fri, Aug 06, 1999 at 03:46:34PM -0700, Joey Hess wrote:
> > Correct section 3.3 to take account of file-rc (#41547)
> > * Proposed by Julian Gilbey; seconded by Roland Rosenfeld.
> > * Part of policy doesn't make sense if file-rc is being used. This
> > proposal is to clean it up so it does make sense, and moreover so
> > it emphasizes that update-rc.d is the only thing that should be
> > used to register init scripts.
>
> I second this proposal too, on the grounds that it mainly clarifies
> existing practice, and where it doesn't it improves compatability amongst
> packages.
>
> Julian, would you like to do the "detailed rewriting" now?
OK, the proposed patch follows my signature.
Julian
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, Dept of Maths, QMW, Univ. of London. [EMAIL PROTECTED]
Debian GNU/Linux Developer, see http://www.debian.org/~jdg
--- policy.sgml.orig Mon Aug 9 18:35:16 1999
+++ policy.sgml Mon Aug 9 19:02:44 1999
@@ -1260,7 +1260,18 @@
state (or `runlevel') is changed (see <manref name="init"
section="8">).</p> <p>
- These scripts are being referenced by symbolic links in
+ There are at least two different, yet functionally equivalent,
+ ways of handling these scripts. For the sake of simplicity,
+ this document describes only the symbolic link method.
+ However, it may not be assumed that this method is being used,
+ and any manipulation of the various runlevel behaviours must be
+ performed using <prgn>update-rc.n</prgn> as described below and
+ not by manually installing symlinks. For information on the
+ implementation details of the other method, implemented in the
+ <tt>file-rc</tt> package, please refer to the documentation of
+ that package.</p> <p>
+
+ These scripts are referenced by symbolic links in
the <tt>/etc/rc<var>n</var>.d</tt> directories. When
changing runlevels, <prgn>init</prgn> looks in the
directory <tt>/etc/rc<var>n</var>.d</tt> for the scripts
@@ -1379,17 +1390,20 @@
<heading>Managing the links</heading>
<p>
- A program is provided, <prgn>update-rc.d</prgn>, to make
- it easier for package maintainers to arrange for the
+ A program is provided, <prgn>update-rc.d</prgn>, to handle the
proper creation and removal of
- <tt>/etc/rc<var>n</var>.d</tt> symbolic links from their
+ <tt>/etc/rc<var>n</var>.d</tt> symbolic links, or their
+ functional equivalent if another method is being used. This
+ may be used by maintainers in their packages'
<tt>postinst</tt> and <tt>postrm</tt> scripts.</p>
<p>
You should use this script to make changes to
- <tt>/etc/rc<var>n</var>.d</tt> and <em>never</em> include
- any <tt>/etc/rc<var>n</var>.d</tt> symbolic links in the
- actual archive.</p>
+ <tt>/etc/rc<var>n</var>.d</tt> and <em>never</em> either
+ include any <tt>/etc/rc<var>n</var>.d</tt> symbolic links in the
+ actual archive or manually create or remove the symbolic links
+ in maintainer scripts. (The latter will fail if an alternative
+ method of maintaining runlevel information is being used.)</p>
<p>
By default <prgn>update-rc.d</prgn> will start services in
@@ -1397,8 +1411,11 @@
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 <tt>/etc/rc<var>n</var>.d</tt>.</p>
+ runlevels by either running <prgn>update-rc.d</prgn>, by
+ simply adding, moving, or removing the symbolic links in
+ <tt>/etc/rc<var>n</var>.d</tt> if symbolic links are being
+ used, or by modifying <tt>/etc/runlevel.conf</tt> if the
+ <tt>file-rc</tt> method is being used.</p>
<p>
To get the default behavior for your package, put in your
