least document /etc/ptmp;
while i'm at it, might as well tidy it up and make it consistent across
these pages;

OK millert@

Therefore added math.h to SYNPOSIS.
OK millert@

"suggest parentheses around && within ||"
ok millert@

feedback and ok espie@

ok jmc@

ok millert

ok millert@ ray@

Based on a diff from Mike Belopuhov.  OK jmc@

OK jmc and millert.

OK otto@

Document that getopt_long(3) can and will accept unique abbreviated long
option names.  This feature has been present since getopt_long(3) was first
released in NetBSD 1.5.  This is also standard GNU getopt_long(3) behavior.
ok millert

from FreeBSD.  With help from jmc@.

trailing newline in contrast to fgetln(3).
ok ray@ jmc@ millert@

Sync the documentation in getpid with arc4random's format.

some time ago--it caused too many problems.

ok deraadt millert

immediately after.
OK millert@.

No binary change with NLS enabled.
ok otto millert espie

in ints since there are multiple flavors.  The key point to get
across is that when storing as a type > byte it may be necessary
to do byte swapping depending on the machine's byte order.
Noticed by Tamas TEVESZ.

sizeof(buf) - 1 to sizeof(buf), since fgets takes the whole buffer size.
Based on diff from Charles Longeau <chl at tuxfamily dot org> long ago.
OK millert@.

Try to tell what this really does.
Including a BUGS section on why it doesn't.
*roff code by wiz@, with some input from
Slava Semushin <slava.semushin@gmail.com>
ok millert

done by arc4random(); ok millert@ deraadt@

to get random data without calling getpid(), ok millert@ deraadt@

ok jmc@

err.h.
OK moritz@ and jaredy@.

in low-mem conditions; ok dim@

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

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

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

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

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@

own brains out, and then takes lint down with it.  To be investigated...