Age | Commit message (Collapse) | Author |
|
|
|
pflog headers. reported by jmc@, tested by jmc@ and sthen@, ok sthen@
|
|
from ARG_MAX to 64K.
Fixes glob-using programs (notably ftp) able to be triggered to hit
resource limits.
Idea from a similar NetBSD change, original problem reported by jasper@.
ok millert tedu jasper
|
|
|
|
- Update local engines for the EVP API change (len u_int => size_t)
- Use hw_cryptodev.c instead of eng_cryptodev.c
- Make x86_64-xlate.pl always write to the output file and not stdout,
fixing "make -j" builds (spotted by naddy@)
ok naddy@
|
|
There's not much use for the declassified cipher from the 80's
with a questionable license these days. According to the FIPS
drafts, Skipjack reaches its EOL in December 2010.
The libc portion will be removed after the ports hackathon.
djm and thib agree, no objections from deraadt
Thanks to jsg for digging up FIPS drafts.
|
|
Revert the "set -e" additions and kill unneeded subshells. ok djm@
|
|
u_long on i386. suggested by deraadt@ and kettenis@
|
|
amd64
|
|
|
|
|
|
|
|
|
|
|
|
that didn't already have one, and then immediately use it in libc's
SYS.h
ok miod@
|
|
|
|
|
|
|
|
OK deraadt@
|
|
|
|
|
|
|
|
|
|
line up nicely. OK deraadt@
|
|
we don't provide the silly union to decompose the value. This will allow
userland to flip the ``flush denormalized to zero'' setting, which apparently
is being relied upon by tcl.
Asked by jasper@ a long time ago. Riding upon the upcoming libc major crank.
|
|
kernel in kern(9), and remove it from OpenSSH.
ok deraadt@, djm@
|
|
information that is looked up while matching glob(3)s
Keeping this information around can make a big difference when
fetching it is expensive, e.g. in sftp which uses GLOB_ALTDIRFUNC
feedback millert@ jmc@
"get it in before the libc crank" deraadt@
|
|
OK deraadt@, millert@
|
|
revert that part of yesterday's diffs;
|
|
|
|
and don't generate clock ticks (ie don't invoke the sio_onmove(3)
call-back).
|
|
deal with this.
ok miod@
|
|
another local variation;
|
|
present in upstream sources, so it must be a local bug;
|
|
- wide character (noun)
- wide-character (adjective)
this is the "fix of least resistance", and appears to be in line with
posix style; a tiny fix still needed for curses, but i'll mail that
upstream;
|
|
these are not built by default, but only built when MANPS is set.
kristaps@ and jmc@ agree with the idea,
and the patch doesn't bother deraadt@ at all
|
|
My problem, canacar@'s fix.
ok sthen@ canacar@
|
|
someone else already has open. OK jmc@
|
|
feedback and ok jmc@, ok millert@
|
|
- bump posix revision and remove xpg; from millert
ok millert
|
|
libform, libmenu, libpanel and each library is also linked to a
corresponding "w" version.
This is a major bump for all four libraries.
Thanks to landry, stsp, sthen, naddy, oga, Martin Pieuchot, and anyone
else I've forgotten for testing.
ok naddy krw deraadt
|
|
Update our sources appropriately. OK deraadt@ jsg@
|
|
was not being done for poll and select, so after fork they would remain
using the same socketpair for signal notification, leading to a race
between the two processes to read from it and hangs.
Problem originally reported by kili@.
ok gilles
|
|
idiotically accepts more then two hex digits following the \x, even
on platforms where a char has 8 bits. It is therefore dangerous to have
an almost-bit-not-quite compatible format in vis(3).
The VIS_ALL (encode all characters) option introduced in the same commit
remains.
|
|
|
|
via setenv() or putenv(). OK miod@
|
|
and VIS_HEX - use C89 \xff style hexadecimal encoding.
Teach unvis(3) how to deal with the hex encoding.
feedback and ok millert@ chl@
|
|
fix NULL vs 0, etc. No behaviour change.
|
|
machdep.console_device that's only implemented on a few architectures.
ok deraadt@, miod@
|
|
now), play and record directons may be out of sync, and since the play
direction is used as clock source, we may end up with data ariving
_before_ the time it was recorded. This breaks the sndio ``device
model'' and most full-duplex apps relying on it, starting with aucat
in its default mode.
Workaround this by using the direction that's ahead as clock source,
ensuring that recorded data never arrives before the clock tick it was
recorded. This prevents apps from crashing but won't fix stuttering
caused by missed interrupts.
ok deraadt@
|