Theodore Ts'o wrote:
Are you using your system with hardware time set to some non-GMT local
time zone? (i.e. /etc/defaults/rcS has UTC="no")
you are, of course, correct. And its interesting in that I had set it to
UTC at some point and I remember having trouble with my timezones and so
forth (my clock in KDE kept getting munched) but the problem went away.
hmmmm...
I think you can make the problem go away by making /etc/localtime
contain a copy of what it is currently symlinked to in
/usr/share/zoneinfo/<timezone>, and renaming
/etc/rcS.d/S22hwclockfirst.sh to /etc/rcS.d/S09hwclockfirst.sh. This
is obviously not the "proper" fix; since among other things if the
localtime file needs to get updated (for example if the US Congress
changes the definition of daylight savings time), we need a way to
make sure /etc/localtime gets updated when the package gets updated.
But I believe if you were to apply the above as a workaround, it
should address your problem. Fixing this in the more global sense
will require making changes in the overall Debian boot setup, and I'm
going to have to take this up on debain-devel and consult other Debian
developers.
Well, I'm all for doing things the "right" way and will fix my clock and
then unpin apt for e2fsprogs and move back up to 1.39. Thanks for your
attention to this matter, and I hope my info will help to continue
improvement of Debian for all ;)
A
Regards,
- Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
