Date: Fri, 3 Aug 2001 14:02:17 -0400 From: Garrett Rooney <rooneg@electricjellyfish.net> To: Garance A Drosihn <drosih@rpi.edu> Cc: Josh M Osborne <stripes@iamsofired.com>, hackers@FreeBSD.ORG Subject: Re: Does /dev/bpf work with kevent? Message-ID: <20010803140217.D51247@electricjellyfish.net> In-Reply-To: <p05101000b79094a295d3@[128.113.24.47]>; from drosih@rpi.edu on Fri, Aug 03, 2001 at 01:51:20PM -0400 References: <20010803102640.A11972@torb.pix.net> <p05101000b79094a295d3@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 03, 2001 at 01:51:20PM -0400, Garance A Drosihn wrote: > At 10:26 AM -0400 8/3/01, Josh M Osborne wrote: > >I'm attempting to use kevent with /dev/bpf to check to see if it > >is ready for reads, but it seems to always return ready to read, > >but the reads get EAGAIN. > > > >Does /dev/bpf not work with kevent? Or should I look elsewhere > >for my bug (like forgetting some random ioctl)? > > > >If you can't use /dev/bpf can ng_bpf and ng_socket somehow be used? > >Any examples of either, or both laying around somewhere? (I've > >never used the netgraph stuff before -- as cool as netgraph looks > >I haven't had the need) > > Are you trying this on current or stable? current has a bug fix > to bpf which still hasn't been merged to stable. sorry, i know i said i'd get you that patch, but my FreeBSD machines still aren't hooked up to the net, so i haven't had a chance to update to -STABLE in a long time... guess it'll have to wait until after 4.4 ;-( unfortunately, i don't think that'll effect kevent. it seemed to be pretty localized to select, although i must admit, i don't know all that much about how kevent works under the hood. -- garrett rooney Unix was not designed to stop you from rooneg@electricjellyfish.net doing stupid things, because that would http://electricjellyfish.net/ stop you from doing clever things. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010803140217.D51247>