ok deraadt@

ok deraadt@

The API exposes controls of modern audio hardware and sndiod software
volume knobs in a uniform way.  Hardware knobs are exposed through
sndiod.  Multiple programs may use the controls at the same time
without the need to continuously scan the controls.
For now sndiod exposes only its own controls and the master output and
input volumes of the underlying hardware (if any), i.e. those
typically exposed by acpi volume keys.
ok deraadt

This is needed in case a foobar fails to start but still returns 0. Changing its
flags (in rc.conf.local) would then get ignored because of this cache (which is
around to handle stop/check/reload on flags changes).
claudio@ reported this issue when struggling with prometheus several weeks ago

"prefix-set" blocks work with line breaks just fine,
probably old macro leftover.
OK job claudio

effectively reverting r1.9 to follow principal of least surprise
"this is fine" millert
"i agree with direction" schwarze

does not work. Make that more clear in the log and ntpdctl -s status.
report by and ok benno@

similar to what deraadt@ recently did in other manual pages.

manual pages that document the corresponding configuration files;
OK jmc@, and general direction discussed with many

Starting from "Combined Table of Contents" in Doug McIlroy's
"A Research UNIX Reader" a table of which edition manuals appeared in.
Checked against manuals from bitsavers/TUHS and source from TUHS where
available.
Ingo points out there are cases where something is included but not
documented until a later release.
bcd(6)		v6	v7
printf(3)	v2	v4
abort(3)	v5	v6
system(3)	v6	v7
fmod(3)		v5	v6
ok schwarze@

the ntp timestamp wrapping in 2036.

keep command-line arguments again; ok aja@ djm@

ok visa@, kettenis@, deraadt@

because each invocation will grow the path, but that exposed an interaction
with loginShell:true in our dot.Xdefaults...

OK millert@

with help from claudio@

1 of 10-100 startups').  "makes sense" deraadt@
Beware if you have multiple sshd processes (e.g. on different ports) and
want to restart/stop just one - with the current proctitle there's no way
to distinguish between these so rc.d/rcctl will match all of them.

"route -q" already silences all standard output;  if it still prints
something, that's a bug to fix in route.
OK bluhm

at the first non-option argument.
I had to read source code to figure it out.

wild fits inside 32 elements, like UsmUserEntry objects.
OK rob@, claudio@

check that the resulting db works instead of some more specific test
okay schwarze@

ok deraadt@

okay millert@, tb@

From j@bitminer.ca with input from Andras Farkas, deraadt, joerg@netbsd
"fix however you feel best!" jmc

While FIDO/U2F keys were already supported by the generic uhid(4)
driver, this driver adds the first step to tighten the security of
FIDO/U2F access.  Specifically, users don't need read/write access to
all USB/HID devices anymore and the driver also improves integration
with pledge(2) and unveil(2): It is pledge-friendly because it doesn't
require any ioctls to discover the device and unveil-friendly because
it uses a single /dev/fido/* directory for its device nodes.
It also allows to support FIDO/U2F in firefox without further
weakening the "sandbox" of the browser.  Firefox does not have a
proper privsep design and many operations, such as U2F access, are
handled directly by the main process.  This means that the browser's
"fat" main process needs direct read/write access to all USB HID
devices, at least on other operating systems.  With fido(4) we can
support security keys in Firefox under OpenBSD without such a
compromise.
With this change, libfido2 stops using the ioctl to query the device
vendor/product and just assumes "OpenBSD" "fido(4)" instead.  The
ioctl is still supported but there was no benefit in obtaining the
vendor product or name; it also allows to use libfido2 under pledge.
With feedback from deraadt@ and many others
OK kettenis@ djm@ and jmc@ for the manpage bits

repair that.