For open/openat, if the flags parameter does not contain O_CREAT, the
3rd (variadic) mode_t parameter is irrelevant. Many developers in the past
have passed mode_t (0, 044, 0644, or such), which might lead future people
to copy this broken idiom, and perhaps even believe this parameter has some
meaning or implication or application. Delete them all.
This comes out of a conversation where tb@ noticed that a strange (but
intentional) pledge behaviour is to always knock-out high-bits from
mode_t on a number of system calls as a safety factor, and his bewilderment
that this appeared to be happening against valid modes (at least visually),
but no sorry, they are all irrelevant junk. They could all be 0xdeafbeef.
ok millert

As done everywhere else, use a local version of MINIMUM() and avoid
conflict against a potential define min() from some other scope.

Saw a mention somewhere a while back that the gotdata() function in
here could creates non-uniformity since very short fetches of 0 would
be excluded. blocks of 0 are just as random as any other data, including
blocks of 4 4 4.. This is a misguided attempt to identify errors from the
entropy churn/gather code doesn't make sense, errors don't happen.
ok bcook

branches: 1.5.2; 1.5.8;
Update the link for the getentropy(2) manual to man.openbsd.org/

ok deraadt@

unify files further

unify versions, so they are easier to diff.

mix in more virtual memory and process information

add initial HP-UX getentropy/arc4random support.

patch from Kinichiro Inoguchi, tested on HP-UX 11.31

ok deraadt@

As done everywhere else, use a local version of MINIMUM() and avoid
conflict against a potential define min() from some other scope.

Saw a mention somewhere a while back that the gotdata() function in
here could creates non-uniformity since very short fetches of 0 would
be excluded. blocks of 0 are just as random as any other data, including
blocks of 4 4 4.. This is a misguided attempt to identify errors from the
entropy churn/gather code doesn't make sense, errors don't happen.
ok bcook

branches: 1.5.2; 1.5.8;
Update the link for the getentropy(2) manual to man.openbsd.org/

ok deraadt@

unify files further

unify versions, so they are easier to diff.

mix in more virtual memory and process information

add initial HP-UX getentropy/arc4random support.

patch from Kinichiro Inoguchi, tested on HP-UX 11.31

ok deraadt@

Saw a mention somewhere a while back that the gotdata() function in
here could creates non-uniformity since very short fetches of 0 would
be excluded. blocks of 0 are just as random as any other data, including
blocks of 4 4 4.. This is a misguided attempt to identify errors from the
entropy churn/gather code doesn't make sense, errors don't happen.
ok bcook

Update the link for the getentropy(2) manual to man.openbsd.org/

ok deraadt@

unify files further

unify versions, so they are easier to diff.

mix in more virtual memory and process information

add initial HP-UX getentropy/arc4random support.

patch from Kinichiro Inoguchi, tested on HP-UX 11.31

ok deraadt@

Update the link for the getentropy(2) manual to man.openbsd.org/

ok deraadt@

unify files further

unify versions, so they are easier to diff.

mix in more virtual memory and process information

add initial HP-UX getentropy/arc4random support.

patch from Kinichiro Inoguchi, tested on HP-UX 11.31

ok deraadt@