| Age | Commit message (Collapse) | Author |
|---|
|
problem found by Philip Guenther.
|
|
in the output. this test currently fails; see kernel/6178
|
|
|
|
|
|
OK millert@, deraadt@
|
|
Add a note that the regress depends on the "family" keyword in resolv.conf
OK millert@, deraadt@
|
|
from wiz
|
|
a new test to check it's working correctly. ok deraadt@
|
|
by options in ~/.ssh/config. From Dan Peterson.
|
|
- unbreak, since -r was removed from disklabel(8)
ok otto@
|
|
|
|
Always cool to see email addresses @netbsd/@openbsd in the same program ;)
|
|
- display only section headers in warning messages if -w (asked by jmc@)
- better fix option: have process_line return the processed line, and use
that info.
- return proper line for comments (noticed by Thomas Klausner)
- let more code run always, only display warnings when wanted
- sorting of see also should be case-insensitive (noticed by jmc@)
|
|
allocations, making sure that the union of all space is allocated.
ok deraadt@
|
|
|
|
values to test accuracy of math functions (currently, only double
precision tests are present)
a report summary (fpaccuracy.out) containing max errs in ulp is generated
originally under gpl. consented to relicense it under our license
ok millert@
|
|
cloder@'s email bounces
|
|
|
|
|
|
|
|
|
|
|
|
ok matthieu@
|
|
ok sthen@ miod@
|
|
"ike" rules in ipsec.conf, the default peer is used. In theory
ipsecctl -f ipsec.conf can configure the default peer for each "ike"
entry. As isakmpd only supports one default peer, the last "ike"
rule that uses a default peer wins. This configuration is then
significant for all "ike" rules that use the default peer.
Now a warning is printed if a later rule in ipsec.conf changes the
configuration of the original default peer. This should be an error
but that would break existing user configs. So only a warning is
printed.
ok hshoexer@, todd@
|
|
match what both POSIX and ksh.1 already describe in regards to set
-e/errexit's behavior in determining when to exit from nonzero return
values.
specifically, the truth values tested as operands to `&&' and `||', as
well as the resulting compound expression itself, along with the truth
value resulting from a negated command (i.e. a pipeline prefixed `!'),
should not make the shell exit when -e is in effect.
issue reported by matthieu.
testing matthieu, naddy.
ok miod (earlier version), otto.
man page ok jmc.
|
|
was expecting a certain parser error message. Accepting the ikefail10
config file is not considered to be a bug anymore.
ok hshoexer@
|
|
keyword as argument for the peer parameter will do that. An ike
without peer creates the peer-default config. A flow without peer
acquires a host-to-host SA.
tested by grunk@, todd@, ok grunk@, hshoexer@, todd@
|
|
OK hshoexer@, markus@.
|
|
which might be different on different machines. Use some fixed
addresses instead.
pointed out and ok david@
|
|
use OPENBSD/NETBSD constant to choose the behavior, and have the same
program in both OSes.
Also some minor cleanups, like no longer needing to check for comments
that have been stripped already.
work with wiz@netbsd.org and jmc@
|
|
mode.
|
|
prodded by david@
|
|
the program-part of the buffer size, ie the part that is subject to
underruns. Useful for apps like cdio(1) that don't have their own
rings, or to apps that have a minimum ring size constraint. Setting
the ``bufsz'' parameter becomes deprecated.
ok jakemsr
|
|
|
|
discussed with jmc@ and Thomas Klausner (wiz@netbsd.org)
|
|
|
|
|
|
in sshd -T output
|
|
|
|
from wiz@netbsd
|
|
a regress test by me
|
|
sio_onvol(3) functions. The audio(4) backend tries to use the
inputs.dac, outputs.dac, outputs.output and outputs.master
controls (in this order). Add a sample file in
regress/lib/libsndio/vol/vol.c
|
|
|
|
adding grouping parentheses, compiling whatever's compilable with /o,
restricting words with word boundaries. /b
okay grunk@, jmc@ (with help from jmc@)
#10000 !
Oddly fitting, as my first commit was concerned with manpages as well...
|
|
okay grunk@, jmc@
|
|
Also remove some warnings for OpenBSD, since /pub/OpenBSD
will occur very often in tool samples.
okay grunk@, jmc@
|
|
and clarify the comment above.
ok espie@
|
|
and it greatly improves code flow there. Also, print usage to STDERR instead
of STDOUT. Use an EOF-heredoc instead of a clumsily escaped \t\n-string.
ok espie@
|
|
replace one '&&' by 'and' to not get bitten by operator precedence later on
no functional change otherwise
jmc@ tells me to just go ahead for standard stuff like this.
|
