Index: tcpdump.1
===================================================================
RCS file: /home/ncvs/src/contrib/tcpdump/tcpdump.1,v
retrieving revision 1.10
diff -u -r1.10 tcpdump.1
--- tcpdump.1	23 Jul 2001 23:15:44 -0000	1.10
+++ tcpdump.1	19 Feb 2002 13:42:47 -0000
@@ -81,28 +81,6 @@
 \fITcpdump\fP prints out the headers of packets on a network interface
 that match the boolean \fIexpression\fP.
 .LP
-.B Under SunOS with nit or bpf:
-To run
-.I tcpdump
-you must have read access to
-.I /dev/nit
-or
-.IR /dev/bpf* .
-.B Under Solaris with dlpi:
-You must have read/write access to the network pseudo device, e.g.
-.IR /dev/le .
-.B Under HP-UX with dlpi:
-You must be root or it must be installed setuid to root.
-.B Under IRIX with snoop:
-You must be root or it must be installed setuid to root.
-.B Under Linux:
-You must be root or it must be installed setuid to root.
-.B Under Ultrix and Digital UNIX:
-Once the super-user has enabled promiscuous-mode operation using
-.IR pfconfig (8),
-any user may run
-.BR tcpdump .
-.B Under BSD:
 You must have read access to
 .IR /dev/bpf* .
 .SH OPTIONS
@@ -164,12 +142,6 @@
 If unspecified, \fItcpdump\fP searches the system interface list for the
 lowest numbered, configured up interface (excluding loopback).
 Ties are broken by choosing the earliest match.
-.IP
-On Linux systems with 2.2 or later kernels, an
-.I interface
-argument of ``any'' can be used to capture packets from all interfaces. 
-Note that captures on the ``any'' device will not be done in promiscuous
-mode.
 .TP
 .B \-l
 Make stdout line buffered.  Useful if you want to see the data
@@ -210,7 +182,7 @@
 .TP
 .B \-s
 Snarf \fIsnaplen\fP bytes of data from each packet rather than the
-default of 68 (with SunOS's NIT, the minimum is actually 96).
+default of 68.
 68 bytes is adequate for IP, ICMP, TCP
 and UDP but may truncate protocol information from name server and NFS
 packets (see below).  Packets truncated because of a limited snapshot
@@ -1633,22 +1605,6 @@
 .RS
 patches@tcpdump.org
 .RE
-.LP
-NIT doesn't let you watch your own outbound traffic, BPF will.
-We recommend that you use the latter.
-.LP
-On Linux systems with 2.0[.x] kernels:
-.IP
-packets on the loopback device will be seen twice;
-.IP
-packet filtering cannot be done in the kernel, so that all packets must
-be copied from the kernel in order to be filtered in user mode;
-.IP
-all of a packet, not just the part that's within the snapshot length,
-will be copied from the kernel (the 2.0[.x] packet capture mechanism, if
-asked to copy only part of a packet to userland, will not report the
-true length of the packet; this would cause most IP packets to get an
-error from
 .BR tcpdump ).
 .LP
 We recommend that you upgrade to a 2.2 or later kernel.