*** please update /etc/netstart and test if it works ok for you ***

compiled in, but one disabled, and use config -e to swap them and build
the other kernels; saves valuable compile time.
Add ramdisks into the build (at release time). Since we are moving to a
bsd.rd installation, it is not necessary to put kernels in .tgz files
anymore, so don't bother, and adjust installation script sets information
accordingly.

of silently truncating.  OK deraadt@ otto@

ok deraadt@

fixes pr #3998; diff from frank denis, though slightly different fix
committed;
help and ok millert@

fallout from the deferred dns lookups
noticed by dhartmei@

via mixerctl.conf.
ok deraadt@, earlier version ok henning@

ntp_settime() -> priv_settime()
ntp_host_dns() -> priv_host_dns()

From: Joerg Sonnenberger <joerg@britannica.bec.de>

ok henning@

from otto and myself; prodded by henning;

ok otto@

easier on portable.  ok henning@

anymore, same thing for us and it makes darren's life easier for the
portable

Noticed by mepch@.  OK pedro@ and deraadt@

to an interface; no change in default config
from Toni Mueller <support@oeko.net>, ja ja ja ja bob

ok krw@ millert@

ok markus@ krw@ cloder@ millert@

ok djm@

precision field when we reply in server mode accordingly. from phessler

IBM/Digital API.

plus one

by form@pdp-11.org.ru.
ok todd@ henning@

changes in NetBSD by Christos.  OK otto@

ok drahn@, millert@

inherit rootdelay from the delay from the last client update from the peer
that we picked last time to adjust the local clock.
in some cases we use the average offset between two peers' client updates,
then use the average delay between the two as well.

and such

code path for NTP4 remains unchanged, we already set refid correctly there.
NTP3 and older uses an IPv4 address as refid.
use the IP of the server we last synced to if it was a IPv4 one.
sometimes we use the average offset between two, in that case just pick
one for the IP.
this scheme naturally fails when we query IPv6 servers and have to reply
to IPv4 NTP3 (or even older NTP versions) clients - refid stays at 0 then.
this is a protocol limitation, nothing we can do about it.