retitle 520607 hwclock.sh should require checkroot for start
tags 520607 + patch
thanks

Here is a more correct and tested patch to change the dependency of
hwclock.sh to run just after checkroot.sh, and not in parallel with
hwclockfirst.sh when concurrent booting is enabled.

Here is a proposed changelog entry:

  * Fix init.d/hwclock.sh start dependency information, make it
    start just after checkroot (Closes: #520607).

Please upload this fix to unstable soon. :)

diff -u util-linux-2.16/debian/changelog util-linux-2.16/debian/changelog
--- util-linux-2.16/debian/changelog
+++ util-linux-2.16/debian/changelog
@@ -1,3 +1,11 @@
+util-linux (2.16-2.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+
+ -- Petter Reinholdtsen <[email protected]>  Thu, 06 Aug 2009 22:33:20 +0200
+
 util-linux (2.16-2.1) unstable; urgency=low

   [ Aurelien Jarno ]
diff -u util-linux-2.16/debian/rules util-linux-2.16/debian/rules
--- util-linux-2.16/debian/rules
+++ util-linux-2.16/debian/rules
@@ -107,6 +107,7 @@
            install -m 755 debian/hwclock.sh 
debian/util-linux/etc/init.d/hwclock.sh; \
            install -m 755 debian/hwclock.sh 
debian/util-linux/etc/init.d/hwclockfirst.sh; \
            sed -i -e '/^FIRST=/s/no/yes/' -e '/Provides:/s/ck/ckfirst/' \
+               -e '/Required-Start:/s/checkroot/mountdevsubfs/' \
                -e '/Required-Stop:/s/.local_fs/umountroot/' \
                -e '/Default-Start:/a# Default-Stop:' -e '/Default-Stop:/d' \
                debian/util-linux/etc/init.d/hwclockfirst.sh; \
diff -u util-linux-2.16/debian/hwclock.sh util-linux-2.16/debian/hwclock.sh
--- util-linux-2.16/debian/hwclock.sh
+++ util-linux-2.16/debian/hwclock.sh
@@ -18,7 +18,7 @@

 ### BEGIN INIT INFO
 # Provides:          hwclock
-# Required-Start:    mountdevsubfs
+# Required-Start:    checkroot
 # Required-Stop:     $local_fs
 # Default-Start:     S
 # Default-Stop:      0 6

Happy hacking,
-- 
Petter Reinholdtsen



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

Reply via email to