From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue, 23 Apr 2013 15:30:03 +0200
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Message-ID: <20130423133003.GB19997@polynum.com>
Mime-Version: 1.0
User-Agent: Mutt/1.4.2.3i
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [9fans] Date woes
Topicbox-Message-UUID: 45e9e3b6-ead8-11e9-9d60-3106f5b1d025

I was testing a new version of kerTeX (more changes to my compilation
framework---mainly around Windows Interix support) with Plan9 (new
version released BTW), and I stumbled once upon on date strange
behavior.

IIRC, I did not use this Plan9 node since the CET Saving Time switch.

When verifying a directory listing (fossil) I saw:

The correct date (time) on the file (I mean the correct time in CEST).

An incorrect time on the command line: it was 2 hours _backward_. And
when rebooting, the CMOS was being reset with this 2 hours error (from
UTC).

What I don't get:

1) How can fossil and the system display two different dates? Are they
not using the very same system value?

2) Could it be that fossil takes CMOS and then continue on its own or
takes CMOS constantly, while the kernel (?) takes CMOS, then leaves it
alone, correct (wrongly) and counts in software, overwriting the value
only when rebooting?

3) Is there something related to Windows "compatibility"? I mean,
Windows stores (stored) local time, and is there a variable that
instructs to correct the CMOS value?

Thanks for clues!
--
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C