From: "Boyd Roberts" <boyd@planete.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] undocumented fs config options?
Date: Thu, 10 May 2001 07:31:40 +0200 [thread overview]
Message-ID: <00c101c0d912$7dc36510$e8b7c6d4@SOMA> (raw)
In-Reply-To: <3AF90041.3117.2E7770AE@localhost>
From: "Nigel Roles" <nigel@9fs.org>
>
> The configuration I use is an ARC Galleon Rugby clock receiver
> connected to the cpu server, a small daemon to read the clock
> and set the rtc, and sntpd to serve time to whomever requires it.
do they sell the oregon scientific clocks in the uk? they're the
one's which are synched with an xmitter in germany.
they cost nothing and should be easily converted to do the job.
then again, there's the TAC.
next prev parent reply other threads:[~2001-05-10 5:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-09 4:10 jmk
2001-05-09 7:30 ` Nigel Roles
2001-05-10 5:31 ` Boyd Roberts [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-10 6:00 nigel
2001-05-10 19:46 ` Boyd Roberts
2001-05-08 15:19 anothy
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='00c101c0d912$7dc36510$e8b7c6d4@SOMA' \
--to=boyd@planete.net \
--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).