On 2012-03-04 at 19:30 +0100, Henning Brauer wrote: > * Phil Pennock <[email protected]> [2012-03-04 13:23]: > > https://github.com/syscomet/openntpd > > please note that it takes a bit more for a new portable release, > namely, at least tests on the major platforms.
Absolutely. Couldn't find a test suite, or a changelog of the portable changes, so went about reconstructing via code archaeology. Thus the first commit simply being "got it working on one platform". Can you point me to a test suite or anything else used for the portable production? > > The current CVS of ntpd was imported to the initial branch "openbsd" and > > I branched "master" from that. I then pulled in the imsg stuff from > > current OpenBSD and then went through the FreeBSD Ports packages, > > applying the changes which seemed sane (almost all of them). Only > > *incompatibility* with upstream is storing drift information as parts > > per million, for compatibility with reference ntpd. > > this is an inacceptable difference between a portable and the native > one. Alternative viewpoint: OpenNTPD using an equivalent file format to the reference implementation but with different meanings of the numbers is an unacceptable difference. Switching to the compatible difference and documenting the scale of the numbers lets administrators switch from one implementation to the other while maintaining the same drift file. Lower barriers to switching increases the ability of a sysadmin to try alternatives. That lets them move to us and, equally important, move away again. Sysadmins will not be an expert and will likely resent learning that they experienced problems when trying to switch because the file contents needed to be massaged. If you want to use a different meaning on a platform where you're the base system ntpd, that's questionable but fine. Doing so where you're a third-party addition means you should be renaming the default filename for the drift-file to make it clear that it's "openntpd.drift". I'm keeping this change in. > also, I'd be interested what the other changes are. They're briefly summarised in Porting.txt, which is linked to as README.md, so when you visit the web-page above, you'll see them. -Phil
