Hi all, I'll try to answer all the comments in one go: On Fri, Apr 29, 2011 at 2:43 AM, Heiko Baums <lists@xxxxxxxxxxxxxxx> wrote: > Am Fri, 29 Apr 2011 02:33:57 +0200 > schrieb Tom Gundersen <teg@xxxxxxx>: > >> * We now strongly discourage the use of HWCLOCK="localtime", as this >> may lead to several known and unfixable bugs > > This can lead to problems on multi boot systems on which Arch > Linux is installed parallel to Windows. At least older Windows versions > can't handle hardware clocks which are set to UTC. Windows can be configured to use UTC. If this is not possible, we still support localtime, but it will cause weird bugs. The only change we made was to change the default and to add a comment to rc.conf. Nothing will change on existing systems. > So if there are issues with HWCLOCK="localtime" these should be fixed > instead. I really meant what I said: The problems cannot be fixed, they are conceptual, not implementation specific. I wrote a summary of why systemd does not support localtime, the same problems apply to initscripts (but we have just been ignoring them): <https://wiki.archlinux.org/index.php/Systemd#Why_does_systemd_not_support_the_RTC_being_in_localtime.3F>. I don't think any additional announcement should be necessary, except for the above note on the front page and the comment in rc.conf. It would of course be very helpful if people could update any documentation they find that mentions localtime/UTC. Hope that answered all the questions, Tom
