qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bartosz Fabianowski <bartosz@fabianowski.de>
To: kyle@silverbeach.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Changing RTC from UTC to local time
Date: Sat, 29 May 2004 20:50:29 +0200	[thread overview]
Message-ID: <40B8DB75.5050005@fabianowski.de> (raw)
In-Reply-To: <200405291023.18228.kyle@silverbeach.net>

> Er, no.  For a _Windows_ PC, this is true.  For all *BSD and Linux 
> OSes, you should usually use UTC/GMT for the hardware clock.

You can set a PC's RTC to UTC or any other time zone for that matter if 
you want to. However, according to the original design (dating back to 
the olden days of the first IBM PC), the RTC should be running in local 
time.

I don't run Linux myself but since so many people multi-boot Windows and 
Linux, I guess it must be possible to make Linux deal with an RTC 
running in local time, even if the Linux default is UTC. As for *BSD, it 
is definitely possible to do so. I run FreeBSD as my primary OS and I 
know that during installation it already asks you whether your RTC has 
local or UTC time. So it can deal with both scenarios.

Thus, since Linux and *BSD are flexible and can deal with both the 
standard local and non-standard UTC setting, while Windows only 
understands local time, I believe that setting the RTC to local time 
will make it usable to all those systems at once.

> Please revert the patch or make it so that it is a runtime option.  I 
> don't run Windows in QEMU and this makes all my times off.

I guess one could make this a runtime option. But that would only 
clutter the command line, as there would be one more parameter just to 
set the RTC's time zone. A compile time option makes much more sense 
IMHO. However, this would only benefit very few people as most people 
download binaries.

Keeping in mind that Linux and *BSD both can deal with a standard PC RTC 
running in local time, are you sure that QEMU really needs the option of 
having the RTC run in UTC?

Regards,
- Bartosz Fabianowski

  reply	other threads:[~2004-05-29 18:50 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 [this message]
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
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=40B8DB75.5050005@fabianowski.de \
    --to=bartosz@fabianowski.de \
    --cc=kyle@silverbeach.net \
    --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).