Bug#330227: util-linux: Please add LSB formatted dependency info in init.d script

2007-07-06 Thread Petter Reinholdtsen

You asked during debconf what the correct dependency information for
the hwclock.sh init.d script should be.  Here is a small update.  As
/etc/localtime no longer is a symlink into /usr/, but a copy of the
timezone information, the only thing needed is visible /dev/rtc and a
mounted /etc.  For stopping, it need a mounted local file system.  I
suggest using $local_fs for that.

Because of this, I believe this dependency information
is correct:

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

The hwclockfirst.sh script is removed now, so I do not provide a
header for that script.

Please add this header soon.  the util-linux package is one of the two
base packages without dependency information in the init.d script, and
it would be great if we could start verifying the correctness of the
base system soon.

Happy hacking
-- 
Petter Reinholdtsen


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



Bug#330227: util-linux: Please add LSB formatted dependency info in init.d script

2006-09-09 Thread Petter Reinholdtsen
[Petter Reinholdtsen]
 ### BEGIN INIT INFO
 # Provides:  hwclockfirst
 # Required-Start:
 # Required-Stop:
 # Default-Start: S
 # Default-Stop:
 ### END INIT INFO

I just checked /sbin/hwclock, and based on the use of /dev/rtc, I
believe it should start after mountdevsubfs.  So the header should
look like this:

### BEGIN INIT INFO
# Provides:  hwclockfirst
# Required-Start:mountdevsubfs
# Required-Stop:
# Default-Start: S
# Default-Stop:
### END INIT INFO

Friendly,
-- 
Petter Reinholdtsen


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



Bug#330227: util-linux: Please add LSB formatted dependency info in init.d script

2006-09-09 Thread Petter Reinholdtsen
[LaMont Jones]
 Except that hwclockfirst exists _ENTIRELY_ to run _before_ modules
 are loaded.

Right.  I did not know that.  As long as the LSB-style dependency
information reflect this intention, I am happy, because my dependency
based boot system will then get it all correct. :)

 In fact, I believe that we're pretty close to the point where I can
 drop hwclockfirst entirely, although anyone with /dev/rtc really
 should not be building it as a module, if they want time to be
 correct, at least with older versions of module-init-tools...

Right.  I saw some comments about it being needed on platforms without
kernels setting the clock from hardware.  I guess those kernels are
slowly becoming obsolete. :)

Friendly,
-- 
Petter Reinholdtsen


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



Bug#330227: util-linux: Please add LSB formatted dependency info in init.d script

2006-09-09 Thread LaMont Jones
On Sat, Sep 09, 2006 at 02:46:37PM +0200, Petter Reinholdtsen wrote:
 [Petter Reinholdtsen]
 I just checked /sbin/hwclock, and based on the use of /dev/rtc, I
 believe it should start after mountdevsubfs.  So the header should
 look like this:

Except that hwclockfirst exists _ENTIRELY_ to run _before_ modules are
loaded.  In fact, I believe that we're pretty close to the point where I
can drop hwclockfirst entirely, although anyone with /dev/rtc really
should not be building it as a module, if they want time to be
correct, at least with older versions of module-init-tools...

lamont


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



Bug#330227: util-linux: Please add LSB formatted dependency info in init.d script

2006-09-08 Thread Petter Reinholdtsen

Since I first reported this issue I have learned more on how to
properly document the dependencies, and util-linux is one of the last
packages with init.d scripts in /etc/rcS.d/ without such dependency
information.  Please add dependency info to the scripts, and ignore my
previous proposal and use this instead.

### BEGIN INIT INFO
# Provides:  hwclockfirst
# Required-Start:
# Required-Stop:
# Default-Start: S
# Default-Stop:
### END INIT INFO

### BEGIN INIT INFO
# Provides:  hwclock
# Required-Start:$local_fs $remote_fs
# Required-Stop: $local_fs $remote_fs
# Default-Start: S
# Default-Stop:  0 6
### END INIT INFO

Please verify that this dependency information and runtime list is
correct.  Note that 'default-stop' should be used for the runlevels
calling the script using the 'stop' argument, which happen in runlevel
0 and 6 also for S-type symlinks.

Friendly,
-- 
Petter Reinholdtsen


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



Bug#330227: util-linux: Please add LSB formatted dependency info in init.d script

2005-09-26 Thread Petter Reinholdtsen

Package: util-linux
Version: 2.12p-8
Severity: wishlist

To be able to check boot script order, and also to be able to start
boot scripts in parallel, it is important to know the dependencies of
the various boot scripts.  The Linux Software Base specifies a init.d
header file format useful for this purpose, and adding such header to
the hwclock init.d script would make it possible for me to use this
information to check the current sequence and speed up the debian
boot.

URL:http://refspecs.freestandards.org/LSB_2.1.0/LSB-generic/LSB-generic/initscrcomconv.html
documents the LSB header format.

Here is a proposed dependency header to document the dependencies of
hwclock.sh and hwclockfirst.sh.  It is slightly tested using the
insserv package and the new parallell booting support in sysvinit.

### BEGIN INIT INFO
# Provides:  hwclock
# Required-Start:$local_fs $remote_fs
# Required-Stop: $local_fs $remote_fs
# Default-Start: S 1 2 3 4 5
# Default-Stop:  0 6
### END INIT INFO

### BEGIN INIT INFO
# Provides:  hwclockfirst
# Required-Start:
# Required-Stop: 
# Default-Start: S 1 2 3 4 5
# Default-Stop:  0 6
### END INIT INFO


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