Package: util-linux
Version: 2.12r-14
The priority of hwclock.sh keeps getting bounced around, and currently
it is priority 11, as of 2.12r-14 (and it still is, as of 2.13~rc3-6):
util-linux (2.12r-14) unstable; urgency=low
* Make that 11 for hwclock.sh, since we need / to be writable for the
adjfile.
It really needs to be before S10, so that the time is correct for those
people who want their CMOS clock to tick localtime, and who live east of
the GMT timezone. It was at 8, which worked, but per the problem of /
needing to be writable for adjfile:
util-linux (2.12r-13) unstable; urgency=low
* Move hwclock.sh to 8 since localtime is now a file, not a symlink.
Adds Depends: tzdata (>=2006c-2)
Closes: #342887
The real fix for this is to have hwclock.sh and hwclockfirst.sh, which
unfortunately disappeared here:
util-linux (2.12r-12) unstable; urgency=low
* drop hwclockfirst.sh, and put hwclock.sh back at 50. See #50572 and
Closes: #342887
If you read through all of the bug report for #342887 it makes it very
clear that hwclock needs to be run before S10checkroot, and that
/etc/localtime must be on the root filesystem. The reason for
hwclockfirst.sh was precisely because hwclock needs to be run to adjust
the time before / is remounted read/write.
Hence, I believe the correct answer is to restore hwclockfirst.sh, and
to make it be at run at /etc/rcS.d/S08hwclockfirst.sh.
Thanks for your consideration.
- Ted
P.S. I have my own workaround for this, which involves adding an entry
to /etc/e2fsck.conf
[options]
buggy_init_scripts = 1
which I'm going to have to do for Ubuntu, because of an intransigence
with their installer people (apparently they think users shouldn't be
bothered to set the clock correctly at install time, or be asked what
timezone they are in, so the clock might always be busted after
the install). But hopefully this is one place where Debian can be
better than Ubuntu. :-)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
