More tcpdump 8->1 cleanup.

Approved by:	mlaier
MFC after:	3 days

2 files changed, 9 insertions, 6 deletions

diff --git a/contrib/pf/man/pf.os.5 b/contrib/pf/man/pf.os.5
index f4bdeda..07e0927 100644
--- a/contrib/pf/man/pf.os.5
+++ b/contrib/pf/man/pf.os.5
@@ -13,6 +13,9 @@
 .\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+.\"
+.\" $FreeBSD$
+.\"
 .Dd August 18, 2003
 .Dt PF.OS 5
 .Os
@@ -23,7 +26,7 @@
 The
 .Xr pf 4
 firewall and the
-.Xr tcpdump 8
+.Xr tcpdump 1
 program can both fingerprint the operating system of hosts that
 originate an IPv4 TCP connection.
 The file consists of newline-separated records, one per fingerprint,
@@ -200,7 +203,7 @@ An absolutely braindead embedded operating system fingerprint could be:
 .Ed
 .Pp
 The
-.Xr tcpdump 8
+.Xr tcpdump 1
 output of
 .Bd -literal
   # tcpdump -s128 -c1 -nv 'tcp[13] == 2'
@@ -214,7 +217,7 @@ almost translates into the following fingerprint
   57344:64:1:44:M1460:	exampleOS:1.0::exampleOS 1.0
 .Ed
 .Pp
-.Xr tcpdump 8
+.Xr tcpdump 1
 does not explicitly give the packet length.
 But it can usually be derived by adding the size of the IPv4 header to
 the size of the TCP header to the size of the TCP options.
@@ -236,7 +239,7 @@ three bytes.
 .Pp
 In the above example, the packet size comes out to 44 bytes.
 .Sh SEE ALSO
+.Xr tcpdump 1 ,
 .Xr pf 4 ,
 .Xr pf.conf 5 ,
-.Xr pfctl 8 ,
-.Xr tcpdump 8
+.Xr pfctl 8
diff --git a/contrib/pf/man/pfsync.4 b/contrib/pf/man/pfsync.4
index cde2f7e..10fc5a6 100644
--- a/contrib/pf/man/pfsync.4
+++ b/contrib/pf/man/pfsync.4
@@ -42,7 +42,7 @@ table used by
 .Xr pf 4 .
 .\" XXX: not yet!
 .\" State changes can be viewed by invoking
-.\" .Xr tcpdump 8
+.\" .Xr tcpdump 1
 .\" on the
 .\" .Nm
 .\" interface.