Ethereal-dev: Re: [ethereal-dev] Viewing packets while capturing...

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Lyle Bickley <lpb@xxxxxxxx>
Date: Wed, 06 Jan 1999 17:18:42 -0800
Lyle Bickley wrote:
> 
> Guy Harris wrote:
> 
> > I can't speak for BSD/OS.  I have the impression that the POSIX threads
> > libraries for {Free,Net,Open}BSD are userland-only; I don't know if they
> > also have a wrapper library.
> 
> > It may be that some of the platforms listed are ones of which few enough
> > users would want to use Ethereal that we don't have to worry about them
> > - but I wouldn't necessarily *assume* that of any platform.  I
> > *definitely* wouldn't assume no {Free,Net,Open}BSD user would care about
> > Ethereal, and probably wouldn't assume that about BSD/OS, either.
> 
> We've got Free BSD 2.2.6 running in our lab as well.  I'll check it out.

I checked out Free BSD pthread implementation (applicable to Net BSD as
well) and found that it was what Guy Harris suggested it might be in
many SVR4 UNIX systems, namely:

1) No native threads;
2) When "make world" is done with WANT_LIBC_R defined, a pthreads
library is created as well as a thread safe libc called "libc_r".
3) All thread scheduling is done by pthread code - not in the kernel.
4) pthread does use non-blocking kernel pipes (_thread_kern_pipe and
_thread_sys_close.

The question is:  Are we (Guy, et al) SURE that pthreads implemented in
this manner won't accomplish what we need done - namely capturing and
displaying data "at the same time"??

Cheers,
Lyle
-- 
Lyle P. Bickley  |  Bickley Consulting West Inc.
lpb@xxxxxxxxxxx  |  1697 Grant Road
V 650-428-0621   |  Mountain View, CA 94040
F 650-428-0599   |