From FreeBSD via Ed Maste:
install's -o and -g flags both accept a name or a numeric argument.
In -U -M (non-root METALOG) mode it always emitted uname= and gname= in
the METALOG, but these are not appropriate for numeric IDs.
If the -o and/or -u arguments parse as an ID, emit uid= and/or gid=
respectively.
Note that if an argument is valid as both a name and numeric ID we will
prefer the name in normal (non -U -M) mode and the ID in -U -M mode. We
don't want to require a passwd db in non-root mode, and entirely-numeric
user or group names are a terrible idea so just accept this discrepancy.
PR: 284119
Add example to use xmodmap to remap Option to Command key.
Clarification on keys that generate middle and right button events.
Clarification for brightness keys on mac68k.
Addresses PR/59011.
bwi(4): Add support for Nintendo Wii WLAN.
Adapt the bwi(4) driver to support SDIO attachment and driving TX/RX using
PIO instead of DMA since the latter is not supported on SDIO busses.
tests/gcov: demonstrate wrong coverage report after vfork/exec
Discovered in usr.bin/make, function Cmd_Exec.
The coverage test I ran on 2024-07-13 was still good. I don't remember
the exact version of NetBSD-current I was running back then.
With NetBSD-current from 2025-01-17, gcov does not report full coverage
data after a vfork/exec call. Running the test program inside ktrace
shows that after a vfork call, the child process writes its coverage data
back, probably right before the exec call, but the parent process
doesn't.
Running a child process through system(3) is not affected; there,
posix_spawn is used instead of vfork/exec.
Half revert the previous.
Only use cprng_fast32() for in kernel (ie: #ifdef _KERNEL) usages,
leave rump (and anything else userland) doing it the old way.
