half of Diana's problem) ok todd

ok drahn@

stats' and 'rndc recursing' commands in /var/named/tmp (instead of
/var/named), which is writable by the 'named' user.
feedback and ok jakob@ deraadt@, also agreed by fkr@ and msf@

ok krw@

err.h.
OK moritz@ and jaredy@.

last_sensor_scan == 0. monotime might be very close to 0 after boot.
source unknown, maybe from naddy, rediscovered & ok mblamer

okay theo

in low-mem conditions; ok dim@

Mention errno, pw_file, and pw_init in pw_lock man page.
OK jmc@, otto@, millert@, and deraadt@.

ok miod@, deraadt@

with deraadt@ some time ago

ok drahn@

ok henning@ deraadt@

/etc/isamkpd.  Noticed by ajacoutot@lphp.org, thanks!
ok mcbride

This makes it readable by unprivileged uses, simplifying configuration,
and there is no reason for it to be secret.
ok msf deraadt hshoexer

of the last sensor update time got broken, doesn't show up with gps since
it updates often (more often than we read), but naddy ran into it with dcf.
record time of last sensor datum seperately. ok naddy balmer

rc checks pflog0 existance before starting pflogd0, pbly to not print an
error message on pflog-less kernels... ugh. ok mcbride

working again.
help from millert@, ok deraadt@ pedro@

<molivier at users dot sourceforge dot net>
ok jmc@ mickey@

and deleted. previously this script only generated diffs for existing
files.
ok lots of people including millert@ msf@ mcbride@ todd@ and probably more.

includes used a bit later (for instance on the vax)

ok claudio@

codebase.  tested mostly by ckuethe and myself.  __dtoa() use now requires
a call to __freedtoa()

time, and make ntpd use that to send the next uery to an ntp peer and the
like. this has the advantage that changes to the clock do not interfere
with the intervals. for example, when we start on machines without an
RTC and the initial settime (-s) kicks in, intervals were strange.
idea from amandal@entrisphere.com, this implementation by me
tested ckuethe, phessler, mbalmer, ok mbalmer

(output logs are still umask 077)
"i think this is right" deraadt@

them only every 30 seconds. now query them every 5,and take the median
value from 7 queries as sensor value. this takes outliers out of the
equation and makes the overall result much better, especially for
sensors with heavy jitter (like nmea for now)

create special allocators for pginfo and pgfree structs instead of imalloc.
this keeps them separated from application memory.
for chunks, to prevent deterministic reuse, keep a small array
and swizzle the to be freed chunk with a random previously freed chunk.
this last bit only for chunks because keeping arbitrarily large regions
of pages around may cause out of memory issues (and pages are, to some
extent, returned in random order).
all changes enabled by default.
thanks to ben for pointing out these issues.
ok tech@

From: amandal@entrisphere.com