adjust the note in STANDARDS: passing args to the flags is not an
extension, it's just we do it differently;

ok millert
use reallocarray
okay gilles@
A #define to rename another #define which is then used only once introduces
more obscurity than clarity. Nuke DHCPD_LOG_FACILITY and just use
LOG_DAEMON in openlog() call.
Document that v?dprintf() is just as safe as v?snprintf().  OK espie@
Move include to the top and nuke pointless comments.
Calling signal once to ignore SIGPIPE is sufficient - we do not need to do
this again in each app.

ok miod@
Replace (sometimes conditional) use of alloca with malloc, and clearing
through volatile pointers with explicit_bzero().

ok beck@ jsing@
Stop pulling signal.h into apps.h - just include it from openssl.c where
it is needed.
signal.h is not needed here.
Clean up the SSL cipher initialisation and use C99 initialisers for
clarity, grepability and to protect from future field reordering/removal.

ok miod@
Make DEBUG a bit easier to use by calling setlogmask(LOG_UPTO(LOG_DEBUG))
when it is set, and the current setlogmask(LOG_UPTO(LOG_INFO)) when it
is not set.
Not OPENSSL_SYS_SUNOS.
We have stdio and are not WIN16.
Take an axe to rc5speed.c - strip out everything that is for other
platforms.
clean up after the traphandler children, otherwise they will live on
as zombies. ok blambert
Expose bif_capacity as the 'design capacity' through an acpibat sensor,
giving you the original capacity of the battery:

hw.sensors.acpibat0.watthour0=64.07 Wh (last full capacity)
hw.sensors.acpibat0.watthour4=84.24 Wh (design capacity)

hw.sensors.acpibat0.amphour0=2.03 Ah (last full capacity)
hw.sensors.acpibat0.amphour4=4.40 Ah (design capacity)

Diff from Fabian Raetz on tech@, thanks!

ok mlarkin@ zhuk@ armani@ kettenis@
Make the signal handler safe: block signals when updating data-structures
that are walked by routines called from the signal handler and use
dprintf() instead fprintf() in ar_close().

ok millert@
Use REG_STARTEND to permit searches to work past/across NUL bytes.

ok millert@ shadchin@
Don't print a "weird flag" type warning "[b2&3=0x2400]" for DNS NOTIFY
messages which should be sent with AA set. Adapted from a patch at
http://marc.info/?l=tcpdump-patches&m=98115734907026&w=2 pointed out by
Peter J. Philipp, ok henning@
Archives written with a non-standard blocksize currently show up as
truncated reads.  Until better detection of that case can is implemented,
back out that part of rev 1.45

problem noted by sthen@