From: Bartosz Fabianowski <bartosz@fabianowski.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Changing RTC from UTC to local time
Date: Mon, 31 May 2004 16:20:29 +0200 [thread overview]
Message-ID: <40BB3F2D.4030709@fabianowski.de> (raw)
In-Reply-To: <877jus3dp4.fsf@Janik.cz>
> On the other hand, I agree that having the possibility to change CMOS
> time to local could be handy for those who use broken systems like
> Microsoft Windows is.
Seems like we all agree on this. The only thing we can't agree on is
what should be the default. I believe local RTC is a sane default while
you believe it should be UTC. Really, all I care about is that I am
given the option of using local RTC if I need to. Since QEMU is not my
project and I have no commit privileges, I hope that Fabrice will pick
the way he prefers and then commit my patch - modified or unmodified.
> +1. Also imagine you boot your system in 2:30 the day when time moves
> back from 03:00 to 02:00, ie. there are two moments 02:30. Which one
> it is?
Yes, as I said many times before, a local time RTC is neither elegant
nor without problems. Neither is the A20 gate. But when emulating a PC,
you have to live with other people's bad decisions and you have to
emulate them faithfully. IBM's and later Microsoft's choice to go with a
local time RTC is something one needs to be aware of and that one needs
to emulate - not something one needs to agree with.
> My system in US always gives me right time now - it is in UTC [...]
And with my patch, there would be nothing there to keep you from doing
it like this. Just specify "-utc" on the command line and you are fine.
> You still think like Windows only user. Please stop that.
No, I am not thinking like a Windows user. I am thinking *about* Windows
users while you prefer to ignore them. Truth is, most Linux/*BSD people
are smart enough to figure out what the difference between local time
and UTC is and to decide which one they want. While, on the other hand,
most Windows people are simple end users who don't understand this
choice. To them, when the RTC runs in UTC, the clock will simply be off
by a few hours and they will have no clue why. That's why I believe
local time should be the default, with a well documented and easily
accessible option to override this default if you choose to do so.
- Bartosz
next prev parent reply other threads:[~2004-05-31 14:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 14:39 [Qemu-devel] Changing RTC from UTC to local time Bartosz Fabianowski
2004-05-29 17:23 ` Kyle Hayes
2004-05-29 18:50 ` Bartosz Fabianowski
2004-05-29 23:13 ` Tim
2004-05-29 23:23 ` Bartosz Fabianowski
2004-05-30 4:52 ` John R. Hogerhuis
2004-05-30 19:32 ` Bartosz Fabianowski
2004-05-30 19:42 ` Kyle Hayes
2004-05-31 13:53 ` Pavel Janík
2004-05-31 14:20 ` Bartosz Fabianowski [this message]
2004-05-31 14:51 ` Fabrice Bellard
2004-05-31 14:51 ` Bartosz Fabianowski
2004-05-31 15:12 ` Derek Fawcus
2004-05-31 16:43 ` Tim
2004-05-31 16:27 ` Pavel Janík
2004-05-31 17:09 ` Kyle Hayes
2004-05-30 21:59 ` Flavien
2004-05-31 0:29 ` Bartosz Fabianowski
2004-05-31 1:52 ` Kyle Hayes
2004-05-31 12:11 ` Bartosz Fabianowski
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=40BB3F2D.4030709@fabianowski.de \
--to=bartosz@fabianowski.de \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).