machinery minimally cope with this.
Discussed with and reluctantely accepted by deraadt@; we both dislike
losing the ``naturally comes out of your fingers'' kernel names and the
``one size fits all'' logic; but for now I don't see any easy way to
get a single kernel binary able to run on multiple IP## flavours.

the first query we will never do the settime because
SENSOR_QUERY_INTERVAL (30s) is greater than SETTIME_TIMEOUT (15s).  so
during the settime period only, be more aggressive and use
SETTIME_TIMEOUT/3 for the query interval.
ok henning@

ok deraadt@

When set to 0, daily(8) won't send mail unless there is something to report.
Using feedback from kettenis@ henning@ jmc@
OK sthen@ jmc@

in order not to annoy parser scripts and their owners (like henning@)

add the same infrastructure to daily; silencing daily needs another step
discussed with ajacoutot@ okan@ todd@ sthen@ deraadt@ jmc@
"immediately commit" deraadt@ (without seeing the final diff)

in preparation for improvements in /etc/daily and /etc/weekly
using feedback and suggestions from jmc@ and sthen@
ok jmc@, and sthen@ agreed with the general direction

can be fairly sure the terminal is already initialized.  Avoids
a one second pause on login.  Requested and OK deraadt@

and fix two pastos in the printf(1) reporting bad group IDs;
ok okan@

while here, remove the misleading shbang and an unused variable
and add the missing cross reference to ac(8)
ok sthen@ jmc@

not listed in /etc/ttys.  OK deraadt@ guenther@

ridiculous; xdm is totally broken since it never starts anything which resembles
a "login shell".  As a result, no configuration is brought into a process
context to give to future xterms or *sh shells and thus cause them to run their
.profile or .kshrc or such a thing, to get futher configuration.  Therefore
people are left with a totally bland unconfigured Unix environment in their
xterms, and don't know how to change this since .profile is ignored.  This
problem shows hundreds of thousands of google hits.  xdm is fundamentally
broken, but we must solve this also for the startx methods, too, and for people
running csh.  It is clear that .xsession is not a solution to this problem at
all (that is, assuming the people who suggest such a thing really mean a
.xsession file with the execute bit set).  This now becomes the recommended
way for new users to get out of this stupid situation; if someone does not
like it they can change it or delete it.  Few will.  Just watch.
ok kettenis guenther millert

between nick and miod

input & ok theo

files leave.
requested by deraadt@, ok miod@

since we perhaps cannot assume that is what kernels will be in the
pathetically stupid world that SGI created

behaviour here replace by an explicit set reassemble yes no-df.
noticed by Valery Masiutsin <val.masutin at gmail dot com>

build the sets before we build the media.  While there we can get rid
of DESTDIR/snapshot too, and simply install straight into RELEASEDIR.
(This also ends up saving an astounding amount of traffic/latency in a nfs
environment)

-DSHA256_ONLY in order to save space; ok deraadt@

some of the sets)

argument if the argument is deemed to be optional ('::').
feedback and ok jmc@ and millert@

ok miod

makemap as !sendmail versions of this binary are not valid here.
pointed out by and ok sthen@

allocations fails.
looks right deraadt, krw
ok henning

ok deraadt, millert

A package can actually "change" after an update even if its version does
not and yet it will not appear in the security(8) output.
wording by eric@
ok mbalmer@

ok miod@