From owner-svn-src-head@freebsd.org Fri Nov 24 21:57:34 2017 Return-Path: Delivered-To: svn-src-head@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 8298BDF28BC for ; Fri, 24 Nov 2017 21:57:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 433AE66229 for ; Fri, 24 Nov 2017 21:57:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x232.google.com with SMTP id q101so30697858ioi.1 for ; Fri, 24 Nov 2017 13:57:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=d2D0iHvZ5YbMZuwOqjScdNEhh4m6gAoxf49aBfgs5F8=; b=wGrZlUnFEufPq6DAonR1f5LHQFomoeaw+wHQRGtvEV2267ze1HsMYDwkAhGSAc6qT2 d/7wuxY27zZMdkEeCXD2sb5jTom4YU4nqHFf4S4iVElzIDaHC/LccXTTSMI7eIrM2lvM MzN3DE+H9ek0QgFj9YVJ2qqUriXG/h3pxl6/VOYY1XWJ6E6/6Nep9B2wqXWmSmGn5uEm /MA6oDnoLbdFzzt0pzEBooWtaUrb4wllFJyQoiuy6XWAf8VylveSFAd0B1k3YjDk8ZL0 ifxsj6mN/UifF4WQyQ9tLySXIIUulpXfbX2qadXEq0zxjCzPn57JIqviRXjz8eecSvrv QfZw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=d2D0iHvZ5YbMZuwOqjScdNEhh4m6gAoxf49aBfgs5F8=; b=FXwcC9eqNFV9z+XZ/aklc4Oa6ZwgjAIvh9ZexFkDbTZa5M/bCXIWAGGwIDHRtScoOZ SiiyDY4PFVdc9UJy/aNCdB3BcnX9qzD2r5UNH/CHnJnTvHKMiRvX2Nhax27mziPpX8Yf yyiIjXXpQkg0E89gR7pB6ZuSnS2wsyMe1jqL9LQYJMu4UTzxWEyEjW+HNMk8CVatFiwD TdTd9FGFPMaxXWeGRo+O93HruQNWSJjlwJGx+JzQHom0m45wwHDnA39X0kngNkf5736B wnMg4ssECegb4PfXmLpCC/Cux9PcKtWXnn4Cs21hz0FeuBBjR+IQJJnG2sr0Mp9DOySr NxHA== X-Gm-Message-State: AJaThX5/yDb0eILAMMUl3kxSwybkMOIcEFIwmC/SiBVbygHSt66bAckv leMzTnRvZitvpi8j8Vfz5yQrjojUdaM0xOJNAvLEgA== X-Google-Smtp-Source: AGs4zMYAG/c6lnjLzjAHNLSf4So+R20oHZ9Rm/NGCZqa/1PuLP75wHLkepzBZo3PaKKqDb+nkA6NKIqf5ysxrzLgV4Q= X-Received: by 10.107.30.81 with SMTP id e78mr19621002ioe.130.1511560653530; Fri, 24 Nov 2017 13:57:33 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Fri, 24 Nov 2017 13:57:32 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:f964:7c3e:d2:aac5] In-Reply-To: <201711242114.vAOLE4b6097164@pdx.rh.CN85.dnsmgr.net> References: <201711242114.vAOLE4b6097164@pdx.rh.CN85.dnsmgr.net> From: Warner Losh Date: Fri, 24 Nov 2017 14:57:32 -0700 X-Google-Sender-Auth: 4nsa-jXGIfSbGe2MKi5Sfi2zyNU Message-ID: Subject: Re: svn commit: r326095 - head/usr.sbin/bsdinstall/scripts To: "Rodney W. Grimes" Cc: Emmanuel Vadot , Allan Jude , "Conrad E. Meyer" , src-committers , "svn-src-all@freebsd.org" , "svn-src-head@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2017 21:57:34 -0000 On Fri, Nov 24, 2017 at 2:14 PM, Rodney W. Grimes < freebsd@pdx.rh.cn85.dnsmgr.net> wrote: > > > > We are not talking about removing ntpdate in this thread. > > > > Well, after Ian said that it was deprecated I ask if we should remove > > it to be honest. > > And I think we have come to the agreement not to do that until the > official distribution does it as well, is that also correct? > I think we should do whatever Ian suggests. I did time things with atomic clocks and ntpd for about 8 years. He's done them for the same company I have and knows the current set of quirks better than anybody else in this thread. These days, it's generally better to use the freebsd ntp pool, like we have in ntp.conf, and in that scenario, an invocation of ntpd with the appropriate flags can give you almost identical behavior to ntpdate. The 'almost' here has a lot of quibbles that aren't relevant to the installer. And if you don't like the freebsd ntpd pool, then the installer should be writing an appropriate ntpd.conf file anyway, which has the host. It can all be done w/o using ntpdate (note: I didn't say remove it), and once that's in place, and we know there's something not unforeseen, we'll be ready if the ntpd folks ever make good on their threat to kill ntpdate. So remove the use of ntpdate here, but keep the utility around. tl;dr: Do what ever Ian says, if he doesn't do it himself. He's the expert with a decade of daily experience making products with ntpd work and shipping those to customers that have... somewhat diverse environments... Warner