Age | Commit message (Collapse) | Author |
|
|
|
Make knote(9) lock the knote list internally, and add knote_locked(9)
for the typical situation where the list is already locked.
Remove the KNOTE(9) macro to simplify the API.
Manual page OK jmc@
OK mpi@ mvs@
|
|
|
|
|
|
ok kettenis@
|
|
The timecounting code has had stubs for pulse-per-second (PPS) polling
since it was imported in 2004. At this point it seems unlikely that
anyone is going to finish adding PPS support, so let's remove the stubs:
- Delete the dead tc_poll_pps() call from tc_windup().
- Remove all tc_poll_pps symbols from the kernel.
Link: https://marc.info/?l=openbsd-tech&m=167519035723210&w=2
ok miod@
|
|
|
|
|
|
|
|
documentation about it
ok deraadt, miod
|
|
|
|
With Ruby 2.7 in the attic, MODRUBY_REV can no longer be set to 2.7.
It has been possible to set it to 3.2 for a while.
|
|
|
|
xz handles .lz now, we deal with zstd patches by default, bzip2 and gzip
have command variables.
|
|
AMD Elan SC520 has a Am5x86, 486-class processor. We require a
586-class processor.
feedback from jmc@ ok miod@
|
|
efiboot could always boot from CRYPTO and RAID 1, since version 1.5 RAID 1C
also works.
installboot was enabled just now, so only new installations work out of the
box without manual intervention.
|
|
|
|
ok deraadt@ miod@
|
|
|
|
|
|
|
|
|
|
ok yasuoka
|
|
|
|
- Document timeout_abs_ts(9).
- Add the kclock arguments to timeout_set_flags(9) and
TIMEOUT_INITIALIZER_FLAGS(9).
- Document KCLOCK_NONE and KCLOCK_UPTIME.
- Mention the static initialization macros alongside timeout_set(9) etc.;
keep relevant information adjacent.
- Mention timeout_add_sec(9) etc. alongside timeout_add(9); keep
relevant information adjacent.
... plus many other cleanups, rewrites, and rearrangements.
Prompted by mvs@ and many others. With input from jmc@, mvs@, kn@,
schwarze@, and probably a few others I have forgotten.
v1: https://marc.info/?l=openbsd-tech&m=162449274513068&w=2
v2: https://marc.info/?l=openbsd-tech&m=165851505627764&w=2
v3: https://marc.info/?l=openbsd-tech&m=167250339811308&w=2
ok jmc@ mvs@ schwarze@
|
|
|
|
sys/kern/kern_fork.c rev 1.195.
|
|
- Remove the bintime interfaces. They should not be used outside of
the timecounting layer. Unsure whether they warrant a manpage of
their own.
- In the SYNOPSIS, change the variable names for timespec interfaces
from "tv" to "ts".
- Document the new-ish "nsec" interfaces.
- Rewrite the DESCRIPTION. Describe every clock completely in its own
paragraph. Enumerate all the interfaces in tables. Explicitly state
the output format for each interface in said tables. Add new vocab
("hardware", "timestamp") to clarify the differences between the
"get" and non-"get" interfaces.
- Add the CONTEXT, RETURN VALUES, and ERRORS sections.
- Cross-reference clock_settime(2), timeradd(3), and tc_init(9).
Lots of input from schwarze@.
ok jmc@ schwarze@
|
|
ok millert
|
|
|
|
- mention that they can be used for dynamic addressing
- lower the reading order of multicast routing (it makes sense to place
this at the end)
- Xr route(8) up front of the route text, not the end
- use Xr rather than Pa where possible
- reorder the forwarding text
|
|
remove some redundant info regarding netstat -r from ipcomp/ipsec
feedback claudio sthen
ok claudio kn sthen
|
|
A few programs used the plural in their synopsis which doesn't read as
clear as the obvious triple-dot notation.
mdoc(7) .Ar defaults to "file ..." if no arguments are given and consistent
use of 'arg ...' matches that behaviour.
Cleanup a few markups of the same argument so the text keeps reading
naturally; omit unhelpful parts like 'if optional arguments are given,
they are passed along' for tools like time(1) and timeout(1) that obviously
execute commands with whatever arguments where given -- just like doas(1)
which doesn't mention arguments in its DESCRIPTION in the first place.
For expr(1) the difference between 'expressions' and 'expression ...' is
crucial, as arguments must be passed as individual words.
Feedback millert jmc schwarze deraadt
OK jmc
|
|
|
|
|
|
When needed, lladdr is more precise and enduring.
Suggested by deraadt@
Many improvments and OK kn@
|
|
feedback deraadt afresh kn
|
|
|
|
queried by and ok jcw@
|
|
|
|
|
|
|
|
some cases (setrlimit, atomically, only kernel reachable, ...)
|
|
Overriding a default run-regress-* target with custom commands is already
possible and done by many tests. The fact that it currently works depends
on behavior in the BUGs section of make.1, however. The fix is not to add
commands if the target is already defined with commands.
tested by anton
correct fix from espie, ok anton
|
|
|
|
from brad
ok jca
while here knock out the resulting unnecessary Pp and wrap some
long lines
|
|
Original implementation by martijn@
Feedback and suggestions from kn@, sthen@, claudio@, florian@, and deraadt@.
ok deraadt
|
|
Major changes:
* The northern edge of Chihuahua changes to US timekeeping.
* Much of Greenland stops changing clocks after March 2023.
* Fix some pre-1996 timestamps in northern Canada.
|
|
Like that since ports devel/qmake/qmake.port.mk r1.11
Zap qt3 remnants
|
|
|