From owner-freebsd-stable@freebsd.org Fri Jul 10 23:58:28 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 10C2A998C7E for ; Fri, 10 Jul 2015 23:58:28 +0000 (UTC) (envelope-from john.marshall@riverwillow.com.au) Received: from mta1.riverwillow.net.au (mta1.riverwillow.net.au [IPv6:2001:8000:1000:1801::3001]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mta1.riverwillow.net.au", Issuer "Riverwillow 2014 CA Root Certificate" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 12B801112 for ; Fri, 10 Jul 2015 23:58:25 +0000 (UTC) (envelope-from john.marshall@riverwillow.com.au) Received: from mail1.riverwillow.net.au (mail1.riverwillow.net.au [IPv6:2001:8000:1000:1801:0:0:0:4001]) by mta1.riverwillow.net.au (8.15.2/8.15.2) with ESMTPS id t6ANwE66020403 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sat, 11 Jul 2015 09:58:14 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=riverwillow.com.au; s=mta1002; t=1436572694; bh=QuK31tptYjYWPCPWqC/mpawdhLzKJpbSqKMt/Q9TYms=; h=Date:From:To:Subject; b=S5t1dPT2+6eIyYvz8pYXjij3hm/8mgrjpBl63+jft3BV7Fxy+mWblYRwZMwKSa45v 4QOCQf+lDqjJ6sSX5058I/9sHJIYNBXZYJLDE2R+5NFyZNb3IKYsaaJrBMfxSJBlvv cjHDDid7yaf3PjJnvcH+2py/dk9F8iwUfg/yhCZI= Received: from rwpc16.gfn.riverwillow.net.au (rwpc16.gfn.riverwillow.net.au [IPv6:2001:8000:1000:18e1:ae87:a3ff:fe04:b351]) (authenticated bits=56) by mail1.riverwillow.net.au (8.15.2/8.15.2) with ESMTPSA id t6ANwBEI020402 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sat, 11 Jul 2015 09:58:13 +1000 (AEST) Date: Sat, 11 Jul 2015 09:58:11 +1000 From: John Marshall To: freebsd-stable@freebsd.org Subject: Will 10.2 also ship with a very stale NTP? Message-ID: <20150710235810.GA76134@rwpc16.gfn.riverwillow.net.au> Mail-Followup-To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK" Content-Disposition: inline OpenPGP: id=A29A84A2; url=http://pki.riverwillow.com.au/pgp/johnmarshall.asc User-Agent: Mutt/1.5.23 (2014-03-12) 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: Fri, 10 Jul 2015 23:58:28 -0000 --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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.ht= ml 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. --=20 John Marshall --YZ5djTAD1cGYuMQK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlWgXBIACgkQw/tAaKKahKIpJACcDAOfL1uj1Yw8pMivWl8nyomg cH4Anit8mcTW8/KyYjHo5Vsfy2ItVi3x =S86g -----END PGP SIGNATURE----- --YZ5djTAD1cGYuMQK--