Here are patches to add LSB headers to two of the four init.d scripts
in the nslu2-utils package.  I am not sure I understood the
dependencies, so please review.

The last two scripts leds_startup and zleds, have such strange setup,
I was unable to come up with a proposal on how to get it working with
dependency based boot sequencing.  Having both start and stop symlinks
in the same runlevel is not supposed to be working, and I do not
understand why leds_startup exist at all.  It seem to talk about
settings only present when executed from rcS.d/, while being installed
in rc1.d/ .. rc5.d/.  I hope these proposed headers can get you at
least a bit on the way to solving this bug.

diff -ur nslu2-utils-20080403/debian/nslu2-rtc.init 
nslu2-utils-20080403-pere/debian/nslu2-rtc.init
--- nslu2-utils-20080403/debian/nslu2-rtc.init  2008-06-22 12:37:55.000000000 
+0200
+++ nslu2-utils-20080403-pere/debian/nslu2-rtc.init     2008-12-02 
22:47:16.000000000 +0100
@@ -1,2 +1,12 @@
 #!/bin/sh
+### BEGIN INIT INFO
+# Provides:          nslu2-rtc
+# Required-Start:
+# Required-Stop:
+# Should-Start:      udev
+# X-Start-Before:    hwclock
+# Default-Start:     S
+# Default-Stop:
+### END INIT INFO
+
 modprobe rtc-dev
diff -ur nslu2-utils-20080403/files/initscripts/rmrecovery 
nslu2-utils-20080403-pere/files/initscripts/rmrecovery
--- nslu2-utils-20080403/files/initscripts/rmrecovery   2008-06-22 
12:37:56.000000000 +0200
+++ nslu2-utils-20080403-pere/files/initscripts/rmrecovery      2008-12-02 
22:58:21.000000000 +0100
@@ -1,5 +1,12 @@
 #!/bin/sh
-# Run to remove /.recovery if the boot seems to have succeeded
+### BEGIN INIT INFO
+# Provides:          rmrecovery
+# Required-Start:    $remote_fs $all
+# Required-Stop:
+# Default-Start:     1 2 3 4 5
+# Default-Stop:
+# Short-Description: Run to remove /.recovery if the boot seems to have 
succeeded
+### END INIT INFO
 RMRECOVERY=yes
 . /etc/default/rmrecovery || true
 if [ "$RMRECOVERY" != no ]; then



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to