[Pkg-sysvinit-commits] r714 - in sysvinit/trunk/debian: . sysv-rc/doc

[Thomas Hood]

Author: jdthood-guest
Date: 2006-01-29 16:16:14 +0000 (Sun, 29 Jan 2006)
New Revision: 714

Added:
   sysvinit/trunk/debian/sysv-rc/doc/README.Debian
Modified:
   sysvinit/trunk/debian/changelog
Log:
Add README.Debian for sysv-rc

Modified: sysvinit/trunk/debian/changelog
===================================================================
--- sysvinit/trunk/debian/changelog	2006-01-29 15:43:03 UTC (rev 713)
+++ sysvinit/trunk/debian/changelog	2006-01-29 16:16:14 UTC (rev 714)
@@ -21,10 +21,11 @@
     /dev/mapper/* or a swapfile  (Closes: #346329, #348534)
     Don't check for /dev/md* any more, since this was only necessary
     for Linux pre-2.4.
+  * initscripts postinst: Don't run mount{kern,devsub}fs.sh
+  * initscripts postinst: Actually remove some things on purge
   * rcS(5): Improve; mention that if UTC=no then admin must ensure
     that zoneinfo is available
-  * initscripts postinst: Actually remove some things on purge
-  * initscripts postinst: Don't run mount{kern,devsub}fs.sh
+  * Add README.Debian for sysv-rc
 
   [ A Costa / TH ]
   * man pages: 10_doc_manuals.dpatch: Fix a shipload o' typos

Added: sysvinit/trunk/debian/sysv-rc/doc/README.Debian
===================================================================
--- sysvinit/trunk/debian/sysv-rc/doc/README.Debian	2006-01-29 15:43:03 UTC (rev 713)
+++ sysvinit/trunk/debian/sysv-rc/doc/README.Debian	2006-01-29 16:16:14 UTC (rev 714)
@@ -0,0 +1,20 @@
+README for sysv-rc
+------------------
+
+Policy requires that maintainer scripts use update-rc.d to register and
+deregister initscripts.  An unfortunate result of this policy, combined
+with shortcomings in current update-rc.d implementations, is that there
+is no way for maintainer scripts to change the sequence number of an
+initscript that has already been registered if and only if its sequence
+number has not been changed by the administrator.  update-rc.d *never*
+changes the sequence number of an already registered initscript, even
+if its sequence number has not been changed by the administrator.
+There are no plans to fix this problem.  Therefore, if it is necessary
+to change the sequence number of an initscript in order to fix a bug
+then the maintainer script should go ahead and do:
+
+    update-rc.d -f <scriptname> remove
+
+before the new update-rc.d call, even though this overrides out any
+administrator changes.
+