From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: RE: [9fans] dhcp & metanames
Date: Sun, 7 Mar 2004 10:55:41 -0500 [thread overview]
Message-ID: <bde67cc689fba4cc15656bbaea1b87de@plan9.bell-labs.com> (raw)
In-Reply-To: <81132473206F3A46A72BD6116E1A06AE479D33@black.aprote.com>
[-- Attachment #1: Type: text/plain, Size: 277 bytes --]
immediate. It the diff is > 10 seconds it just sets it.
you have some other problem. everyone that dual boots with
windows that doesn't live on the prime meridian (myself
included) is in the same boat.
cd /adm/timezone
cp EET local
reboot and see how things look.
[-- Attachment #2: Type: message/rfc822, Size: 2369 bytes --]
From: "Tiit Lankots" <t.lankots@aprote.ee>
To: <9fans@cse.psu.edu>
Subject: RE: [9fans] dhcp & metanames
Date: Sun, 7 Mar 2004 15:58:18 +0200
Message-ID: <81132473206F3A46A72BD6116E1A06AE479D33@black.aprote.com>
> This means that the system, by reading the RTC on boot, will be in
> the wrong time zone till timesync gets in there. Boot can't do
> any better because the file system with the timezone files hasn't
> started yet at that point.
OK, I'll rephrase. How long will it take for timesync to annihilate a 2-hour
difference?
next prev parent reply other threads:[~2004-03-07 15:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 13:58 Tiit Lankots
2004-03-07 15:55 ` David Presotto [this message]
2004-03-08 14:23 ` Derek Fawcus
-- strict thread matches above, loose matches on Subject: below --
2004-03-07 15:49 Tiit Lankots
2004-03-07 14:31 Tiit Lankots
2004-03-07 15:31 ` David Tolpin
2004-03-07 14:04 Tiit Lankots
2004-03-07 14:13 ` David Tolpin
2004-03-07 13:53 Tiit Lankots
2004-03-07 13:18 Tiit Lankots
2004-03-07 13:15 Tiit Lankots
2004-03-07 13:35 ` David Presotto
2004-03-07 13:51 ` David Tolpin
2004-03-07 10:08 Tiit Lankots
2004-03-07 12:58 ` David Presotto
2004-03-07 13:13 ` David Tolpin
2004-03-07 13:23 ` David Presotto
2004-03-07 13:49 ` David Tolpin
2004-03-07 13:54 ` David Presotto
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=bde67cc689fba4cc15656bbaea1b87de@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--cc=9fans@cse.psu.edu \
/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).