9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Date woes
Date: Tue, 23 Apr 2013 15:30:03 +0200	[thread overview]
Message-ID: <20130423133003.GB19997@polynum.com> (raw)

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



             reply	other threads:[~2013-04-23 13:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 13:30 tlaronde [this message]
2013-04-23 13:34 ` erik quanstrom
2013-04-23 14:34   ` tlaronde
2013-04-23 15:16     ` erik quanstrom
2013-04-23 16:16       ` tlaronde
2013-04-23 16:59         ` erik quanstrom
2013-04-23 17:36           ` tlaronde
2013-04-23 21:55 ` Bakul Shah
2013-04-24 10:52   ` tlaronde
2013-04-24 11:26     ` tlaronde

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=20130423133003.GB19997@polynum.com \
    --to=tlaronde@polynum.com \
    --cc=9fans@9fans.net \
    /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).