From owner-freebsd-stable@freebsd.org Sat Jul 11 05:35:50 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B1D50997716 for ; Sat, 11 Jul 2015 05:35:50 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from dec.sakura.ne.jp (dec.sakura.ne.jp [210.188.226.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 53785D24 for ; Sat, 11 Jul 2015 05:35:50 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from fortune.joker.local (180-198-137-134.nagoya1.commufa.jp [180.198.137.134]) (authenticated bits=0) by dec.sakura.ne.jp (8.14.3/8.14.2/[SAKURA-WEB]/20080708) with ESMTP id t6B52MvQ018922 for ; Sat, 11 Jul 2015 14:02:22 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Sat, 11 Jul 2015 14:02:21 +0900 From: Tomoaki AOKI To: freebsd-stable@freebsd.org Subject: Re: Will 10.2 also ship with a very stale NTP? Message-Id: <20150711140221.41358078ff869022f8464135@dec.sakura.ne.jp> In-Reply-To: <20150710235810.GA76134@rwpc16.gfn.riverwillow.net.au> References: <20150710235810.GA76134@rwpc16.gfn.riverwillow.net.au> Organization: Junchoon corps X-Mailer: Sylpheed 3.4.3 (GTK+ 2.24.27; amd64-portbld-freebsd10.2) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jul 2015 05:35:50 -0000 Hi As head already has 4.2.8 p3 in tree, MFCing this before BETA2 would be nice because... *At least, authorized open stratum 1 by NICT supports only 4.2.6 or later for configuration line (in ntp.conf) like below. pool ntp.nict.jp *This type of configuration is NOT supported by 4.2.4 branch. 4.2.4 still works for now, but NOT supported by NICT. *JST (Japanese Standard Time) is maintained by NICT. http://www.nict.go.jp/JST/JST_E.html http://www2.nict.go.jp/aeri/sts/tsp/PubNtp/index-e.html So syncing to their NTP server by officially supported way with BASE should be nice for Japanese users, I think. Of course, ports has 4.2.8p3. But head also has it. The best way would be MFCing. Is there any problem (with GPS, authenticate, etc.)? On Sat, 11 Jul 2015 09:58:11 +1000 John Marshall wrote: > It's me again with my annual NTP whinge. > > https://lists.freebsd.org/pipermail/freebsd-stable/2013-October/075580.html > https://lists.freebsd.org/pipermail/freebsd-stable/2014-September/079830.html > > Here we are at the start of another release cycle and 10-STABLE still > includes (patched) ntp 4.2.4p8 software that was released in December > 2009. > - ntp 4.2.6 superseded 4.2.4 and was also released in December 2009. > - ntp 4.2.8 superseded 4.2.6 and was released in December 2014. > > Will 10.2 be released with a version of ntp that is two generations old > and that has been legacy since December 2009? > > I am really pleased to see that there has been some recent activity with > respect to ntp in -CURRENT, and that the latest point release (4.2.8p3) > has actually been imported. Is there any likelihood of this being > MFC'd before releng/10.2 is branched? > > Thank you for your patience with me, and thank you to committers who are > working in this space but perhaps not with an eye to -STABLE. I just > think it's really sad that we are shipping very old ntp software with > lots of patches when a current release is available. > > I also note that phk@ was working on an ntp client which he hoped to > offer as a replacement but that is presumably not ready yet. I also > note that we have current versions of ntp available in ports; but I'm > talking about what we ship in the base system. > > -- > John Marshall -- 青木 知明 [Tomoaki AOKI] junchoon@dec.sakura.ne.jp MXE02273@nifty.com