diff options
| author | Patrick McHardy <kaber@trash.net> | 2008-06-02 12:48:48 +0200 |
|---|---|---|
| committer | Patrick McHardy <kaber@trash.net> | 2008-06-02 12:48:48 +0200 |
| commit | 510aef98a56cdbfdb147f78b05d7554bb91770a9 (patch) | |
| tree | e7a4c3413d83c2cb70bb457115001599e819066a /extensions/libxt_physdev.man | |
| parent | 8e1a12fba4008933ce9e89f98c12593e0d39ede3 (diff) | |
manpages: consistent syntax
In the manpages, bold is used to denote characters the user has to
enter verbatim, italic denotes placeholders and non-highlighted
pieces are used as a structure: "[]" specifying an optional part,
"{}" a mandatory part, with "|" used for alternations. The "!" for
negation is better supported before the option than after it, too.
The patch makes a few files consistent with this style already used
in manpages.
Diffstat (limited to 'extensions/libxt_physdev.man')
| -rw-r--r-- | extensions/libxt_physdev.man | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/extensions/libxt_physdev.man b/extensions/libxt_physdev.man index 1e635fc7..a00622a8 100644 --- a/extensions/libxt_physdev.man +++ b/extensions/libxt_physdev.man @@ -3,7 +3,7 @@ to a bridge device. This module is a part of the infrastructure that enables a transparent bridging IP firewall and is only useful for kernel versions above version 2.5.44. .TP -.BR --physdev-in " [!] \fIname\fP" +[\fB!\fP] \fB--physdev-in\fP \fIname\fP Name of a bridge port via which a packet is received (only for packets entering the .BR INPUT , @@ -14,7 +14,7 @@ chains). If the interface name ends in a "+", then any interface which begins with this name will match. If the packet didn't arrive through a bridge device, this packet won't match this option, unless '!' is used. .TP -.BR --physdev-out " [!] \fIname\fP" +[\fB!\fP] \fB--physdev-out\fP \fIname\fP Name of a bridge port via which a packet is going to be sent (for packets entering the .BR FORWARD , @@ -31,12 +31,12 @@ chain. If the packet won't leave by a bridge device or it is yet unknown what the output device will be, then the packet won't match this option, unless '!' is used. .TP -.RB "[!] " --physdev-is-in +[\fB!\fP] \fB--physdev-is-in\fP Matches if the packet has entered through a bridge interface. .TP -.RB "[!] " --physdev-is-out +[\fB!\fP] \fB--physdev-is-out\fP Matches if the packet will leave through a bridge interface. .TP -.RB "[!] " --physdev-is-bridged +[\fB!\fP] \fB--physdev-is-bridged\fP Matches if the packet is being bridged and therefore is not being routed. This is only useful in the FORWARD and POSTROUTING chains. |