| Age | Commit message (Collapse) | Author |
|---|
|
where it has access to the tty width, which is what should have been checked.
|
|
|
|
-f in brackets in the list of options; while here, sort the options
in the manual page.
jmc@ greatly improved the diff fixing a few additional bits on the
manual page.
ok jmc@
|
|
|
|
printed edition of the User's Reference Manual from USENIX and
O'Reilly. 4.4BSD had exactly this, that is much more accurate than
our current description (while here, Jason observed that both FreeBSD
and NetBSD do the same).
tweaked by jmc@
ok jmc@
|
|
the manual page.
ok jmc@
|
|
as well as how the mixer item names are derived.
|
|
ok jakemsr@
|
|
uses of it in our tree.
ok krw@ deraadt@
|
|
no binary change apart from nfsm_reqhead() which is clearly correct.
ok thib@
|
|
and use a static buffer for the footer
|
|
intricately mixed with three minor .Bd fixes
|
|
|
|
of: accept for virtual map "mapname" ...
discussed with jacekm@
|
|
spotted by Ulrich Spoerlein, uqs at spoerlein dot net
|
|
and for a local variable in another function in the same compilation unit;
suggested by Ulrich Spoerlein, uqs at spoerlein dot net
|
|
options but they will all share the same ruleset. this means that there
is no way to have a rule apply to a session established on one listener
but not applied on another.
this commit brings initial support for tagging listeners and having the
rules able to match these specific listeners. The following will define
a rule which will only apply to interfaces tagged as "mynet":
listen on lo0 # implicit lo0 tag
listen on fxp0 tag mynet
listen on fxp1 tag mynet
accept on mynet for domain "example.org" deliver to mbox
|
|
|
|
|
|
teach smtpd how to deliver using specific user permissions:
accept for virtual map "foo" deliver to maildir "/m/%d/%u" user foo
will deliver mail under /m/domain/user as user foo
idea and initial diff discussed with jacekm@
|
|
|
|
bsd) unless some other object has changed. Rebuild and reinstall
in /usr/src/usr.sbin/config/ after updating!
"I like it" deraadt@
|
|
* avoid blank character before the closing ">" of .In
* .Bt can not have children
|
|
* validate and order .Rs child nodes
* underline book title (.%B) and issuer (.%I)
* enclose title of article (.%T) in quotes
* avoid calling mdoc_verr directly, use a proper error code instead
|
|
Actually, our ancient groff behaves slightly differently than this fix,
but not to die is already an improvement. Needs a closer look later.
|
|
|
|
cases (todo: rebuild dependency headers for the complex case...)
|
|
|
|
already done, separate remove/mark_installed in tracker, create a merge
method that allows the merging of updatesets.
|
|
|
|
* newline before .Rs only below SEE ALSO
* newline after .Lb only below LIBRARY
|
|
confused.
|
|
noticed by uqs at spoerlein dot net on FreeBSD,
where <stdlib.h> does not include <sys/types.h>
|
|
as mentioned in the preceding manual commit (oops)
|
|
predefined strings, including the recent sync to new groff
|
|
|
|
|
|
|
|
tables and the supporting infrastructure, mostly in preparation for
HTML output support
|
|
when their action is to be relayed.
|
|
removing unnecessary extra functions
|
|
caused an envelope to be saved with action A_INVALID when it matches
either A_RELAY or A_RELAYVIA.
reported by various people
|
|
|
|
description to reference another. If this is used, any capabilities in the
parent terminal description should override those pulled in by use=.
When cap_mkdb is building terminfo.db, it concatenates any use= references
together so each description is self-contained. However, the ncurses terminfo
implementation doesn't expect this - it assumes it will have to resolve use=
itself, and picks the last entry in the description created by cap_mkdb rather
than the first.
read_bsd_terminfo.c already makes some transformations to make ncurses happy
with the format in the database. So, extend this to trim out duplicate entries,
leaving only the first.
(Interestingly, ncurses already has code to correctly handle merged tc=
capabilities in termcap.db (used if terminfo.db is missing).)
"go ahead" deraadt@
|
|
Tested by bwaichu@yahoo.com.
|
|
implementation since random mmap breaks the default approach.
Note that gcc may not be compiled with PIE support or it will
break this implementation too.
|
|
|
|
|
|
needs to be told to use the nvidia specific quirks to
detect attached devices.
From and tested by minusf@obiit.org
|
|
|
