[Pkg-sysvinit-devel] What's up with hwclock?

[Henrique de Moraes Holschuh]

On Mon, 23 Jan 2006, Petter Reinholdtsen wrote:
> [Henrique de Moraes Holschuh]
> > [Full proposed fix, will work only when all steps are deployed]
> > 
> > Step 1: Get util-linux to run the first hwclock script at the absolutely
> >    earliest possible moment (which is as soon as /dev is available. I think
> >    S05 is about right).   The second script doesn't matter to us, but it
> >    should be run after /etc is writeable because it will be only useful for
> >    doing /etc/adjtime things.
> 
> If you can represent this using the init.d script dependency notation,
> we can use insserv to reorder the boot to see how early the scripts
> can possibly run.

After the entire timezone/localtime mess is fixed, hwclock scripts will have
the following dependencies:

  hwclockfirst:
    - access to hwclock binary
    - access to /dev/rtc on most systems

  hwclock:
    - access to hwclock binary and /dev/rtc
    - access to writeable area where /etc/adjtime is stored

> PS: I hope the your package maintainence isn't often affected by your
>   strong emotions.  Would be a shame to do the wrong thing in affect.

I have a good thick skin and a lot of drive when I am maintaining packages I
feel responsible for, or when fixing bugs that affect me or someone that has
personaly asked me to help.   This issue isn't in either case so far, and I
tacked it just out of a feeling that I wanted things to operate correctly,
and because I already knew how hwclock operated, having done a lot of work
with it a few years ago.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh