svn commit: r326095 - head/usr.sbin/bsdinstall/scripts

[Warner Losh]

On Fri, Nov 24, 2017 at 2:14 PM, Rodney W. Grimes <
freebsd at 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