| Age | Commit message (Collapse) | Author |
|---|
|
|
|
as the onboard ioc device, if one has already been found on this node.
Also, on Origin 300, do not attempt to attach the PS/2 controller on the
onboard ioc(4) since PS/2 ports are not wired.
|
|
|
|
|
|
TGT_ORIGIN, which enables support for all IP27 and IP35 systems. The original
two options have always been used together, and go back to when pefo thought
supporting multiple nodes would be significant work. Since an Origin 200
can be a dual-node system, making a distinction between single node and
multiple node systems is a moot point anyway.
Be sure to rerun config(8) before rebuilding a kernel.
|
|
system type list (which really is the system family) and a subsystem type.
No functional change yet.
|
|
|
|
|
|
|
|
|
|
requested by jmc@
|
|
ok pirofti@
|
|
deleting the ypservers.db file, both in the manual and in the FAQ;
original suggestion to improve this from ajacoutot@,
my wording tweaked by jmc@.
While here, resolve text duplication in the manual.
|
|
ok matthieu@
|
|
|
|
ok henning@ pyr@
|
|
the event will have been freed.
|
|
|
|
anymore, as this causes the nsphy connected to the onboard iec to sometimes
disappear after a warm boot.
Unfortunately this brings back the long reboot times on Origin 200, despite
still asking for no memory test.
|
|
smtp protocol expects lines to end with \r\n.
if a client sends a very long line which is unfortunately read up to \r,
evbuffer_readline() will return the line, then will detect another line
when the buffer is filled again and starts with \n, returning again with
an empty line. this is a bug which trigger very rarely and usually shows
up as an empty line in the middle of headers, causing all subsequent
headers to appear as part of the body to most mail user agents.
upstream fixes this with evbuffer_readln() in version 2.0 of libevent, a
mail will be sent to see if they can backport it, meanwhile we fix it by
introducing evbuffer_readln_crlf().
discussed with and ok jacekm@
|
|
line-by-line (in panes or if ed not supported). Fixes problem spotted by Frank
Terbeck.
|
|
tested by phessler@ pyr@
ok claudio@
"go ahead" deraadt@
|
|
ok oga@
|
|
bogus and misleading error, this permits re-running bridgename.if(5) files etc
without confusion
prodded/found by deraadt@
ok deraadt@ phessler@ henning@ stsp@
|
|
allocate a buffer of the right size.
ok oga@
|
|
ok otto@
|
|
|
|
|
|
partial matches to be done (they wait for further data or a timer to expire,
like a naked escape).
Mouse and xterm-style keys still expect to be atomic.
|
|
following the nat-to changes. Reworked slightly from a diff from eric@.
ok henning jmc
|
|
|
|
|
|
valid map id, then we have no way to know for these structures if they have
a reference to a map, or if the member was not set. make map id start at 1.
|
|
ok gilles@ jacekm@
|
|
ok jacekm@ gilles@
|
|
|
|
The 1yz and 6yz status codes are now removed prior to reporting the status
message in bounce messages, which provides an easy way to distinguish
between local and remote status messages. Initial diff from jacekm@
ok gilles@ jacekm@
|
|
buffer before calling the command print function which can also use it (eg
send-keys).
|
|
free(lkasession) in lka_expand_rcpt()
- while at it, plug a very very unlikely memory leak which i spotted while
reviewing the logic
|
|
tty_key struct.
|
|
- remove prototypes from deprecated functions
|
|
|
|
|
|
only wake up when an event happens.
|
|
complicated because of escape input, but in that case instead of processing a
key immediately, schedule a timer and reprocess the bufer when it expires.
This currently assumes that keys will be atomic (ie that if eg F1 is pressed
the entire sequence is present in the buffer). This is usually but not always
true, a change in the tree format so it can differentiate potential (partial)
key sequences will happens soon and will allow this to be fixed.
|
|
before deleting the writer (reader) otherwise the later
could trigger rpipe_done again.
|
|
|
|
From James Giannoules
|
|
TRY_AGAIN_LATER. NO_CCB is a timer based mechanism that can trivially
be made to fail by running IO to two or more disks simultaneously. The
TRY_AGAIN_LATER thing is more subtle because it now is a permanent
failure instead of transient however this is much harder to hit because
something must have gone wrong before it hits.
ok deraadt krw miod
|
|
from Brad
|
