[Git][NTPsec/ntpsec][master] 3 commits: In "Other user-visible changes", note that pool is now usable.

Eric S. Raymond gitlab at mg.gitlab.com
Tue Oct 4 23:59:11 UTC 2016


Eric S. Raymond pushed to branch master at NTPsec / ntpsec


Commits:
4ecdeca0 by Eric S. Raymond at 2016-10-04T18:37:09-04:00
In "Other user-visible changes", note that pool is now usable.

- - - - -
e33db7a7 by Eric S. Raymond at 2016-10-04T19:15:12-04:00
Update the staleness warning.

- - - - -
8ea267ec by Eric S. Raymond at 2016-10-04T19:58:33-04:00
We don't have a dependency on ntp_gettime.

- - - - -


2 changed files:

- INSTALL
- docs/index.txt


Changes:

=====================================
INSTALL
=====================================
--- a/INSTALL
+++ b/INSTALL
@@ -3,14 +3,13 @@
 == Prerequisites ==
 
 This software should build on any operating system conformant to
-POSIX.1-2001 and ISO/IEC 9899:1999 (C99).  In addition, the
-operating system must have either a Linux-like adjtimex(2) call
-or a BSD-like pair of ntp_gettime(2)/ntp_adjtime(2) calls. Also,
-it must support the IPv6 API defined in RFC2493 and RFC2553. Finally,
-it must support iterating over active UDP interfaces via getifaddrs(3)
-or some equivalent facility.
-
-There are some prerequisites.  Libraries need the library installed
+POSIX.1-2001 and ISO/IEC 9899:1999 (C99).  In addition, the operating
+system must have either a Linux-like adjtimex(2) call or a BSD-like
+ntp_adjtime(2) call. Also, it must support the IPv6 API defined in
+RFC2493 and RFC2553. Finally, it must support iterating over active
+UDP interfaces via getifaddrs(3) or some equivalent facility.
+
+There are some prerequisites.  Libraries need the binary installed
 to run and in addition, the development headers installed to build.
 
 Python 2.x, x >= 6, or Python 3.x >= 3::


=====================================
docs/index.txt
=====================================
--- a/docs/index.txt
+++ b/docs/index.txt
@@ -32,18 +32,6 @@ The Network Time Protocol software contained in this
 distribution is available without charge under the conditions set
 forth in the link:copyright.html[Copyright Notice].
 
-[NOTE]
-It is very important that readers understand that the NTP document
-collection began 25 years ago and remains today a work in progress. It
-has evolved as new features were invented and old features retired. It
-has been widely copied, cached and morphed to other formats, including
-man pages, with varying loss of fidelity. However, these HTML pages are
-the ONLY authoritative and definitive reference. Readers should always
-use the collection that comes with the distribution they use. A copy of
-the online collection at {project-weblink} is normally included in the most
-recent snapshot, but might not agree with an earlier snapshot or
-release version.
-
 This distribution is an implementation of RFC-5905 "Network Time
 Protocol Version 4: Protocol and Algorithms Specification".  NTP is
 widely used to synchronize a computer to Internet time servers or
@@ -63,6 +51,12 @@ in recent decades
 The link:ntpspeak.html[Glossary of NTP-speak] might also be a helpful
 guide for the perplexed.
 
+Use caution when employing search engines to dig up NTP material.
+There are many, many copies of the NTP documentation out there, often
+referring to very old versions and carrying stale information. It's
+best to use only the HTML and manpages that come with your
+distribution.
+
 [[differences]]
 == Differences from NTP Classic ==
 
@@ -164,6 +158,10 @@ few will be user-visible.
 
 === Other user-visible changes ===
 
+* The notorious collision between pool and nopeer in older
+  implementations has been fixed; the pool keyword is now fully
+  usable.
+
 * There is a new data-visualization tool,
   link:ntpviz.html[+{ntpviz}+], which can produce various useful and
   interesting plots from the NTP statistics logs.  These should assist in
@@ -221,8 +219,7 @@ few will be user-visible.
 POSIX.1-2001 and ISO/IEC 9899:1999 (aka C99).  Primary platforms
 include Linux and the *BSD family; any reasonably modern proprietary
 Unix will also serve.  The OS must have either a Linux-like
-adjtimex(2) call or a BSD-like pair of ntp_gettime(2)/ntp_adjtime(2)
-calls.
+adjtimex(2) call or a BSD-like ntp_adjtime(2) call.
 
 Legacy Windows support has been removed from the {project-shortname}
 codebase. Future Windows support will be conditional on the quality



View it on GitLab: https://gitlab.com/NTPsec/ntpsec/compare/1690b3544450ac5d497ecda991646139e1cb70d5...8ea267ec6b87b929e57317536cf4a4948bcd6298
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ntpsec.org/pipermail/vc/attachments/20161004/a0e74187/attachment.html>


More information about the vc mailing list