Age | Commit message (Collapse) | Author |
|
a key binding (L) to move a client back to its last session.
|
|
selection on the right edge but on the left it is.
|
|
const as well.
|
|
than per-client history.
|
|
behave as if the whole code were wrapped in .Bk/.Ek,
i.e. keeping input lines together on output lines.
This is compatible with new groff behaviour and deviates
from historical groff.
Tweaked version of a patch sent by kristaps@ on July 16, 2010.
ok kristaps@ jmc@ sobrado@ millert@
|
|
were dropped.
|
|
corresponding variable to NO.
e.g.
rc_reload=NO
This will save us the trouble of copying the same rc_reload() function
(or others) all over the tree.
ok robert@
|
|
|
|
requested by okan@, ok robert@
|
|
method to handle _class, _user and _shell as we do for _flags.
discussed with and ok ajacoutot@
|
|
and use su to start the daemons.
By default if there is no class defined, daemon will be used. For a shell
it defaults to /bin/sh.
|
|
|
|
just execute su in login emulation mode. from MERIGHI Marcus.
ok millert@, otto@, jmc@
|
|
loop. fixes "login foo" and "su -L foo". ok millert@, otto@
|
|
|
|
entry now that we have the -s option. OK jmc@
|
|
help/ok chl@ nicm@
|
|
of the non-equivalent aliases for it.
ok miod@
|
|
For now, use the simplest conceivable approach, like groff does:
Just a fixed, ugly input stack limit.
Kristaps@ agrees.
|
|
input line together on one single output line.
ok jmc@ and millert@, who also noticed the ugly break.
|
|
`Brq') to have zero arguments without warning. This makes sense because
the multi-line quote macros (`Oo/Oc' etc.) allow zero children anyway.
Furthermore, the documentation doesn't state that they're required to
have children.
Reported by Alex Kozlov, patch from kristaps@.
|
|
Kristaps@ agrees with the idea, even though he didn't review the final patch.
|
|
|
|
|
|
ok millert@
|
|
|
|
to run a different shell than what the password database contains.
Based on a diff from robert@. OK robert@ deraadt@
|
|
scp.c: add -3 to usage()
|
|
time to consume broadcasted messages or the socket gets full and own
messages that are needed are lost. This fixes an infinit loop in
pfkey_reply that happens when bgpd tcp md5sum is used on a system that
also runs a larger IPsec setup.
OK henning, lot of patience, debuging and testing by Thomas Boernert
|
|
number. Without this, isakmpd deletes SAs from the same IP on an
INITIAL-CONTACT message, possibly deleting unrelated NATed tunnels.
Fixes PR 5562. Verified by Mikolaj Kucharski.
ok mikeb@
|
|
transferred through the local host. Without this option the data
is copied directly between the two remote hosts. ok djm@ (bugzilla #1837)
|
|
one bad case of use-after-free after a hell lot of heavy I/O creeping in again
in this driver. This doesn't fix it but will hopefully help me diagnose once
it occurs again.
|
|
|
|
default value of main-pane-width to 80, rather than 81. By Micah Cowan.
|
|
by jmc@ a while back
CVS ----------------------------------------------------------------------
|
|
the 64-bit output/input. On i386, this means that the 64-bit value is in
eax:edx, but on amd64 gcc this is not the case (might be a gcc bug, or might
be intentionally different and annoying?). The consequence is that amd64
errata were not always being matched (and then "corrected" using the magic
repair code). We need to compose/decompose the 64-bit value like the
un-locked msr functions do.
originally pointed out by ragge, ok kettenis jsg
|
|
ok espie@
|
|
|
|
|
|
|
|
ok henning@
|
|
the boot loader passes a variable that identifies the disk its
booting off made up of a bunch of fields like adapter, controller,
disk, and partition offsets, plus a table of all the disks it can
see which includes this id and a checksum.
the kernel goes through and checksums the disks and then maps that
back to the id associated with that disk, and then compares some
of the fields in those ids against the boot disks id to figure out
which disk its on.
the problem is we overflow one of those fields (the disk id one).
since the other fields are set to 0 by the boot loader, this doesnt
really matter that much. however, since those fields are now
significant because of the overflow, we should compare them too.
this prevents sd16 being matched as the boot disk after sd0 on my
system with 25 disks attached.
ok krw@ weingart@
ithe boot loader passes a variable that identifies the disk its
booting off made up of a bunch of fields like adapter, controller,
disk, and partition offsets, plus a table of all the disks it can
see which includes this id and a checksum.
the kernel goes through and checksums the disks and then maps that
back to the id associated with that disk, and then compares some
of the fields in those ids against the boot disks id to figure out
which disk its on.
the problem is we overflow one of those fields (the disk id one).
since the other fields are set to 0 by the boot loader, this doesnt
really matter that much. however, since those fields are now
significant because of the overflow, we should compare them too.
this prevents sd16 being matched as the boot disk after sd0 on my
system with 25 disks attached.
requested by deraadt@
ok krw@ weingart@
|
|
booting off made up of a bunch of fields like adapter, controller,
disk, and partition offsets, plus a table of all the disks it can
see which includes this id and a checksum.
the kernel goes through and checksums the disks and then maps that
back to the id associated with that disk, and then compares some
of the fields in those ids against the boot disks id to figure out
which disk its on.
the problem is we overflow one of those fields (the disk id one).
since the other fields are set to 0 by the boot loader, this doesnt
really matter that much. however, since those fields are now
significant because of the overflow, we should compare them too.
this prevents sd16 being matched as the boot disk after sd0 on my
system with 25 disks attached.
ok krw@ weingart@
|
|
No more functional changes, just sync ordering, comments and white space.
|
|
Kristaps says it is broken and cannot work,
because HTML needs a block structure which .ft does not provide.
Thus, let us just ignore .ft in HTML output.
|
|
and do not bother checking the return values of calls
that always return 1.
From kristaps@.
|
|
ok tobias@ xsa@ nicm@
|
|
ok deraadt@
|
|
window. From Thomas Adam.
|
|
ok tobias@ nicm@
|