Debian bug report logs - #900
tcpdump(1) is unclear re perms and should be tcpdump(8)

Message received at debian-bugs:

From cus.cam.ac.uk!iwj10 Sun May 21 05:55:23 1995
Return-Path: <iwj10@cus.cam.ac.uk>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0sDAXT-0005xIC; Sun, 21 May 95 05:55 PDT
Received: from bootes.cus.cam.ac.uk by pixar.com with SMTP id AA10402
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Sun, 21 May 1995 05:53:56 -0700
Received: by bootes.cus.cam.ac.uk 
	(Smail-3.1.29.0 #36) id m0sDAXN-000BzgC; Sun, 21 May 95 13:55 BST
Received: by chiark
	id m0sCuST-0000XRZ
	(Debian /\oo/\ Smail3.1.29.1 #29.31); Sat, 20 May 95 20:45 BST
Message-Id: <m0sCuST-0000XRZ.ijackson@nyx.cs.du.edu>
Date: Sat, 20 May 95 20:45 BST
From: iwj10@cus.cam.ac.uk (Ian Jackson)
To: Debian bugs submission address <debian-bugs@pixar.com>
Subject: tcpdump(1) is unclear re perms and should be tcpdump(8)

Package: tcpdump
Version: 3.0.3-2

The manual page for the tcpdump program starts:
DESCRIPTION
       Tcpdump  prints  out  the  headers of packets on a network
       interface that match the boolean expression.  Under SunOS:
       You must be root to invoke tcpdump or it must be installed
       setuid to root.  Under Ultrix: Any user can invoke tcpdump
       once the super-user has enabled promiscuous-mode operation
       using pfconfig(8).  Under BSD: Access is controlled by the
       permissions on /dev/bpf0, etc.

However, it doesn't say what the behaviour is under Linux (the same as
SunOS, I believe).

Also, this manpage should clearly be in section 8 rather than 1 (this
affects the page headers in the page as well as the location in the
filesystem, of course).

Ian.