From: Michael Buesch <fsdeveloper@yahoo.de>
To: David Balazic <david.balazic@uni-mb.si>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Wrong clock initialization
Date: Tue, 20 May 2003 20:17:54 +0200 [thread overview]
Message-ID: <200305202018.16062.fsdeveloper@yahoo.de> (raw)
In-Reply-To: <3ECA673F.7B3FB388@uni-mb.si>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 20 May 2003 19:34, David Balazic wrote:
> Hi!
>
> When the kernel is booted ( ia32 version at least ) , it reads
> the time from from the hardware CMOS clock , _assumes_ it is in
> UTC and set the system time to it.
>
> As almost nobody runs their clock in UTC, this means that the system
> is running on wrong time until some userspace tool corrects it.
>
> This can lead to situtation when time goes backwards :
>
> timezone is 2hours east of UTC.
> UTC time : 20:00
> local time : 22:00
>
> System time between boot and userspace fix : 22:00UTC
> System time after fix : 20:00UTC
>
> Comments ?
Why don't you simply set your CMOS clock to UTC?
- --
Regards Michael Büsch
http://www.8ung.at/tuxsoft
20:16:51 up 4:12, 2 users, load average: 1.00, 1.07, 1.24
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+ynFooxoigfggmSgRAopWAJ0YOxEJ5jA3sfNhDwbSHmM5Z2nJQACcDxad
+25XjbOyOGRKYUMtdQtv6mI=
=jE5A
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-05-20 18:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 17:34 Wrong clock initialization David Balazic
2003-05-20 18:08 ` David D. Hagood
2003-05-20 18:10 ` george anzinger
2003-05-20 18:27 ` David Balazic
2003-05-20 20:21 ` george anzinger
2003-05-20 18:17 ` Michael Buesch [this message]
2003-05-20 18:26 ` David Balazic
2003-05-20 20:16 ` Jan Harkes
2003-05-21 11:38 ` Jesse Pollard
2003-05-21 17:00 ` Jerry Cooperstein
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200305202018.16062.fsdeveloper@yahoo.de \
--to=fsdeveloper@yahoo.de \
--cc=david.balazic@uni-mb.si \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox