From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BUnel-0006FD-P0 for qemu-devel@nongnu.org; Mon, 31 May 2004 10:20:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BUnek-0006F1-8O for qemu-devel@nongnu.org; Mon, 31 May 2004 10:20:51 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BUnek-0006Ey-5K for qemu-devel@nongnu.org; Mon, 31 May 2004 10:20:50 -0400 Received: from [81.209.184.159] (helo=dd2718.kasserver.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BUneS-0001Pk-QI for qemu-devel@nongnu.org; Mon, 31 May 2004 10:20:33 -0400 Received: from [192.168.0.7] (dsl-082-083-133-246.arcor-ip.net [82.83.133.246]) by dd2718.kasserver.com (Postfix) with ESMTP id D0C8312F33 for ; Mon, 31 May 2004 16:18:52 +0200 (CEST) Message-ID: <40BB3F2D.4030709@fabianowski.de> Date: Mon, 31 May 2004 16:20:29 +0200 From: Bartosz Fabianowski MIME-Version: 1.0 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> <877jus3dp4.fsf@Janik.cz> In-Reply-To: <877jus3dp4.fsf@Janik.cz> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 > 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