From owner-freebsd-hackers  Fri Feb 17 05:03:02 1995
Return-Path: hackers-owner
Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id FAA07546 for hackers-outgoing; Fri, 17 Feb 1995 05:03:02 -0800
Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id FAA07535 for <hackers@freebsd.org>; Fri, 17 Feb 1995 05:02:54 -0800
Received: from utis156.cs.utwente.nl by utrhcs.cs.utwente.nl (5.0/csrelayMX-SVR4_1.0/RB)
	id AA00733; Fri, 17 Feb 1995 14:02:50 --100
Received: by utis156.cs.utwente.nl (4.1/RBCS-1.0.1)
	id AA23509; Fri, 17 Feb 95 14:02:42 +0100
To: hackers@FreeBSD.org
Subject: Re: tcpdump 3.0? 
In-Reply-To: Your message of Fri, 17 Feb 1995 04:52:11 PST
Date: Fri, 17 Feb 1995 14:02:42 +0100
Message-Id: <23508.793026162@utis156.cs.utwente.nl>
From: Andras Olah <olah@cs.utwente.nl>
content-length: 632
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

On Fri, 17 Feb 1995 04:52:11 PST, "Jordan K. Hubbard" wrote:
> If libpcap is of general utility, and not just good for tcpdump, then
> it should live in /usr/src/lib/libpcap.  If otherwise, then it should be
> next to the tcpdump sources (tcpdump becomes a two-level directory structure)
> as you say.

`libpcap, a system-independent interface for user-level packet
capture.  libpcap provides a portable framework for low-level
network monitoring.  Applications include network statistics
collection, security monitoring, network debugging, etc.' (from the
README).

I'd suggest /usr/lib/libpcap* if there're no objections.

Andras