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: Re: [9fans] Date woes
Date: Wed, 24 Apr 2013 12:52:09 +0200	[thread overview]
Message-ID: <20130424105209.GA529@polynum.com> (raw)
In-Reply-To: <20130423215532.7D855B82A@mail.bitblocks.com>

On Tue, Apr 23, 2013 at 02:55:32PM -0700, Bakul Shah wrote:
>
> Finally if you are running Windows 7 *and* have a recent
> hotfix 2800213 installed, you *can* use UTC in RTC by registry
> entry RealTimeIsUniversal=1. Or so I am told! Finally, 20+
> years later, microsoft does the right thing when they could've
> fixed this in 3.1.

Yes... But I have no Windows (except an XP _home_ sold with my old
laptop) so the RTC was in UTC. But termrc was timesync'ing with
"-L"---and I don't thing I even deal with this, since I played with a
total re-install when finding how to install Plan9 without a CD reader
or network (installing it from another OS already installed on the
disk).

What I still don't get is precisely how the fileserver could have the
right time, when the date displayed by the shell was wrong. It they both
use the same source (the kernel) how can this happen? Except that termrc
hence timesync(8) is run after the fileserver are launched, and then
are taking rtc but correcting it with the timezone (and perhaps the -L),
meaning that the fileserver will always use the time served by the
kernel from the RTC as UTC, while later program will use an user
specification to interpret the RTC.

The "-L" is a Windows thing but is in userland modifying a value that is
taken as is before userland is run...

--
        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-24 10:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 13:30 tlaronde
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 [this message]
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=20130424105209.GA529@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).