From owner-freebsd-hackers  Sun Feb  7 16:02:48 1999
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA07760
          for freebsd-hackers-outgoing; Sun, 7 Feb 1999 16:02:48 -0800 (PST)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA07737;
          Sun, 7 Feb 1999 16:02:39 -0800 (PST)
          (envelope-from fenner@parc.xerox.com)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <52229(4)>; Sun, 7 Feb 1999 16:02:31 PST
Received: by crevenia.parc.xerox.com id <177534>; Sun, 7 Feb 1999 16:02:20 -0800
From: Bill Fenner <fenner@parc.xerox.com>
To: des@flood.ping.uio.no, fenner@parc.xerox.com
Subject: Re: Regarding tcpdump and plip
Cc: hackers@FreeBSD.ORG, nsouch@FreeBSD.ORG, wpaul@FreeBSD.ORG
Message-Id: <99Feb7.160220pst.177534@crevenia.parc.xerox.com>
Date: Sun, 7 Feb 1999 16:02:10 PST
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Ugh.  Can you tell what mode the device is going to be in when you
bpf_attach()?  (Presumably not).  I guess bpf might end up needing
a mechanism to change what you told it in bpf_attach().  I wonder what
happens if someone's got a bpf open on the device when that happens;
probably nothing good...

  Bill

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message