although arguments to `ip proto' and `ether proto' are keywords, and do

need to be escaped, they are not shell keywords;

this wording seems to have been introduced when the page was mdoc'd;
it now matches (more or less) how it was, and {F,N}BSD pages;

found by naddy@

1 files changed, 7 insertions, 9 deletions

diff --git a/usr.sbin/tcpdump/tcpdump.8 b/usr.sbin/tcpdump/tcpdump.8
index 1747567ee90..3e2a7b5a716 100644
--- a/usr.sbin/tcpdump/tcpdump.8
+++ b/usr.sbin/tcpdump/tcpdump.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: tcpdump.8,v 1.50 2005/01/02 18:15:02 jmc Exp $
+.\"	$OpenBSD: tcpdump.8,v 1.51 2005/01/22 09:18:41 jmc Exp $
 .\"
 .\" Copyright (c) 1987, 1988, 1989, 1990, 1991, 1992, 1994, 1995, 1996
 .\"	The Regents of the University of California.  All rights reserved.
@@ -551,15 +551,11 @@ of protocol type
 can be a number or one of the names
 .Cm icmp ,
 .Cm udp ,
-.Cm nd ,
 or
 .Cm tcp .
-The identifiers
-.Cm tcp ,
-.Cm udp ,
-and
-.Cm icmp
-are also shell keywords and must be escaped.
+These identifiers are also keywords and must be escaped
+using a backslash character
+.Pq Sq \e .
 .It Cm ether broadcast
 True if the packet is an Ethernet broadcast packet.
 The
@@ -589,7 +585,9 @@ can be a number or a name like
 .Cm arp ,
 or
 .Cm rarp .
-These identifiers are also shell keywords and must be escaped.
+These identifiers are also keywords and must be escaped
+using a backslash character
+.Pq Sq \e .
 In the case of FDDI (e.g.,
 .Dq Cm fddi protocol arp ) ,
 the protocol identification comes from the 802.2 Logical Link Control