From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BUnGQ-0005h2-M5 for qemu-devel@nongnu.org; Mon, 31 May 2004 09:55:42 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BUnGO-0005fo-HW for qemu-devel@nongnu.org; Mon, 31 May 2004 09:55:42 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BUnGO-0005fV-Ez for qemu-devel@nongnu.org; Mon, 31 May 2004 09:55:40 -0400 Received: from [160.218.40.132] (helo=janik.cz) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BUnFt-0000k3-6M for qemu-devel@nongnu.org; Mon, 31 May 2004 09:55:12 -0400 Subject: Re: [Qemu-devel] Changing RTC from UTC to local time References: <40B8A0B1.3040601@fabianowski.de> <200405291023.18228.kyle@silverbeach.net> <40B8DB75.5050005@fabianowski.de> <20040529231327.GC1690@sentinelchicken.org> <40B91B89.9000500@fabianowski.de> <1085892773.25895.68.camel@aragorn> <40BA36CA.6070805@fabianowski.de> From: Pavel@Janik.cz (=?iso-8859-2?q?Pavel_Jan=EDk?=) Date: Mon, 31 May 2004 15:53:43 +0200 In-Reply-To: <40BA36CA.6070805@fabianowski.de> (Bartosz Fabianowski's message of "Sun, 30 May 2004 21:32:26 +0200") Message-ID: <877jus3dp4.fsf@Janik.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: quoted-printable Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org From: Bartosz Fabianowski Date: Sun, 30 May 2004 21:32:26 +0200 This is multi-reply. > Attached is a revised patch. With this patch, the default time zone > for the RTC is the local time zone of the host. If the command line > option "-utc" is specified, the time zone changes to UTC. I vote against this change. It is nonsense to have local time in UTC because then when you work on the system that has TZ1 time in BIOS and yo= u work in TZ2, you can't set your time accordingly, because you must know t= he TZ1 vs. TZ2 offset. It *should* be enough to know your own timezone to se= t the correct date and time. On the other hand, I agree that having the possibility to change CMOS tim= e to local could be handy for those who use broken systems like Microsoft Windows is. From: Flavien Date: Sun, 30 May 2004 23:59:49 +0200 > Conclusion : setting RTC to local time is a _broken_ concept. +1. Also imagine you boot your system in 2:30 the day when time moves bac= k from 03:00 to 02:00, ie. there are two moments 02:30. Which one it is? From: Bartosz Fabianowski Date: Mon, 31 May 2004 14:11:18 +0200 > > RTC. The host OS will provide the correct time as the fake RTC va= lue. >=20 > My point exactly. Your host operating system is most likely one you = use > quite a lot so chances are you will have set it up correctly to take > care of DST adjustments. I often run QEMU on my other system I have in US. I'm in Europe. I do not want to *always* have bad time... My system in US always gives me right time now - it is in UTC so it is pretty easy to setup - just say the TZ y= ou want to have in your host system. I can't imagine how I could do that should the system use US local time if I want to use Czech local time. > b) a safe default that makes all OSes work - which is local time You still think like Windows only user. Please stop that. This is not saf= e default. This would be default that hurts many people, but not Windows users. This is not "safe". --=20 Pavel Jan=EDk That's the problem: pretesters aren't finding many more bugs nowadays, so it'll probably take until 2005 to find and fix enough bugs that we can comfortably announce the code stable. -- Stefan Monnier in comp.emacs