Date: Fri, 20 Oct 1995 06:56:31 -0700 From: "Jordan K. Hubbard" <jkh@FreeBSD.org> To: marino.ladavac@aut.alcatel.at Cc: John Birrell <jb%cimaxp1@werple.net.au>, hackers@FreeBSD.org Subject: Re: NetBSD/FreeBSD (pthreads) Message-ID: <3087AA8F.2781E494@FreeBSD.org> References: <9510201221.AA26512@atuhc16.aut.alcatel.at>
next in thread | previous in thread | raw e-mail | index | archive | help
marino.ladavac@aut.alcatel.at wrote: > > to be. So we changed libc to allow for threads. We build it twice, once with a > > preprocessor definition _THREAD_SAFE and once without it. For the threaded > > version, a few extra source files are compiled. We always link against libc, > > never libpthread.a and _then_ libc. The MIT implementation tries to sit on top > > of a system like FreeBSD/NetBSD. We believe that it should be part of it. Sorry, I'm coming into this late. This is interesting in that it's almost word-for-word identical to the proposal that was being floated around the table when David and I last talked to Chris Provenzano a USENIX or so back. I find it strange that they would be unreceptive now.. In any case, this was the proposal that I certainly liked best and (I think) David as well. One library without the extra bloat, another compiled to be thread safe. Fine! When can we have the diffs? :-) > > We've ported all our non-threaded code to FreeBSD (2.0.5R). With the exception > > of the function in the kernel which locates SYSVSHM segments, there were no > > problems. (NetBSD fixed SYSVSHM a few months ago. 2.0.5R behaves as NetBSD Could you perhaps elaborate on this a bit? It would certainly be good to fix any brokenness that exists in our SYSVSHM code, if it exists. > > did). We're currently writing widgets so that we don't rely on Motif. Then all > > we need is libc in FreeBSD to be ported to support pthreads and we have our > > factory process monitoring and control product ready to go under FreeBSD. Hmm! I'd be very interested to hear any reports you'd be willing to share about your customers experiences with FreeBSD and your product, when and if you have situations where they're deployed together. It's always good to know how our stuff behaves in the field! :) -- Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3087AA8F.2781E494>