| Age | Commit message (Collapse) | Author |
|---|
|
|
|
actions. Allow interfaces to be specified in special table entries for
the routing actions. Lists of addresses can now only be done using tables,
which pfctl will generate automatically from the existing syntax.
Functionally, this deprecates the use of multiple tables or dynamic
interfaces in a single nat or rdr rule.
ok henning dlg claudio
|
|
|
|
* remove bogus '\\' entry, it is not a correct way to render a backslash
* fix column width specifications (problem noted by jmc@
and cause found by kristaps@)
* mandoc_char(7) is not a utility (noticed by deraadt@)
* improve wording of first sentence (from jmc@)
* add OpenBSD RCS-Id (from jmc@)
* kill whitespace at EOLs (from jmc@)
ok kristaps@, "formatting looks good now" jmc@
|
|
- remove text concerning unsupported character device stuff
- remove text concerning unsupported RXIOC* ioctls
all of this stuff is from miod
|
|
files. If any information found in these documents is worthwhile and you
miss it, please make the time to work it into the manual pages (which people
actually do read).
ok guenther
|
|
man(7) and mdoc(7) special characters and predefined strings in general;
just as mandoc(1) is not intending to implement new languages,
but provide standard formatting for man(7) and mdoc(7) files,
whatever "standard" may mean in this context (sigh).
So move this to the right place.
noticed by deraadt@
|
|
Use non-breaking spaces to reduce the number of arguments.
This now formats correctly with both groff(1) and mandoc(1).
ok jmc@ sobrado@
|
|
instead, .It is required. Thus, move .Pp and text before the .Bl,
and remove the .Pp altogether where it is not needed.
Syntax errors found by mandoc(1), also required to fix the mandoc build;
feedback and ok jmc@, and sobrado@ also supports the direction.
|
|
syntax errors found by mandoc(1), also required to fix the mandoc build;
feedback and ok jmc@ and sobrado@
|
|
also required to fix the mandoc build.
"fine. even if mandoc goes nowhere, it has found some bugs ;)" jmc@
ok sobrado@
|
|
indicator". Even groff(1) does not in general seem very well-behaved
with respect to it, and it is not clear what advantage it might have
compared to '\"', the good old "beginning of comment" escape sequence.
Regarding the case at hand, it is breaking the mandoc(1) build,
and i checked that we get no output change from groff(1).
ok jmc@
|
|
Syntax errors found by mandoc(1), also required to fix the mandoc build.
ok jmc@
|
|
|
|
|
|
|
|
|
|
|
|
ok millert@, help and ok jmc@
|
|
ok guenther
|
|
as SUIDSKIP internally relies on find(1) -path,
it won't work with trailing slashes.
found the hard way by paul de weerd@
ok jmc@
|
|
|
|
point people at where they should be looking instead.
ok espie@
|
|
|
|
|
|
|
|
|
|
|
|
(and remove a duplicate entry in Makefile)
|
|
reference to rgephy. From Brad.
|
|
|
|
|
|
|
|
|
|
|
|
- Remove mentioning PCI in the Silicon Graphics adapter
name. This isn't in the name of the adapter from the
marketing material.
from Brad.
|
|
supported by the driver below the list of supported hardware. From Brad.
|
|
to the description of fpa(4); while here, synchronize the description
of fpa(4) in pci(4).
ok claudio@
|
|
leaving the ioctl description by now, until we see if it is needed
(claudio@ has noted that the ioctl description is a copy from
inet(4), so it would need to be reworked).
ok claudio@
|
|
|
|
ok deraadt
|
|
accepted which are simpler for people (or install scripts) to generate.
Anything else is passed to ifconfig, unmolested.
ok jmc todd
|
|
|
|
|
|
o only stop processing if inet or inet6 lines are malformed
o everything not a specially handled bit is passed to ifconfig unmangled
noticed by several after the move from bridgename.bridge0 -> hostname.bridge0
prodded by deraadt@, tested by and feedback from several
man page bits 'look fine' jmc@
|
|
|
|
Man page advices by jmc@.
|
|
|
|
|
|
|
