From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fsconfig: ipsntp: sntp =~ ntp?
Date: Wed, 1 May 2002 18:43:04 +0100 [thread overview]
Message-ID: <b432fbb06ea79864ab6dc3d51566c866@caldo.demon.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 97 bytes --]
it implements a stripped-down version of NTP,
and you can use it to talk to a full ntp server.
[-- Attachment #2: Type: message/rfc822, Size: 2671 bytes --]
To: 9fans@cse.psu.edu
Subject: [9fans] fsconfig: ipsntp: sntp =~ ntp?
Date: Wed, 01 May 2002 19:23:47 +0200
Message-ID: <200205011723.g41HNlv22373@zamenhof.cs.utwente.nl>
Silly question, unrelated to 4th ed.: is sntp == ntp?
Rephrased: can I use this to talk with 'any' ntp server?
or indicates the 's' something special?
(from browsing the code, it just talks with the ntp port)
Axel.
next reply other threads:[~2002-05-01 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 17:43 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-01 17:23 Axel Belinfante
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=b432fbb06ea79864ab6dc3d51566c866@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--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).