From owner-freebsd-hackers  Tue Sep  9 18:42:07 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA24009
          for hackers-outgoing; Tue, 9 Sep 1997 18:42:07 -0700 (PDT)
Received: from kf0yn.ampr.org ([204.176.110.190])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA24002
          for <freebsd-hackers@freebsd.org>; Tue, 9 Sep 1997 18:42:04 -0700 (PDT)
Received: from [44.50.32.7] (kf0yn-mb.ampr.org [44.50.32.7]) by kf0yn.ampr.org (8.8.5/8.6.5) with ESMTP id UAA13775; Tue, 9 Sep 1997 20:41:38 -0500 (CDT)
X-Sender: cmf@44.50.32.6
Message-Id: <v03102800b03ba458f3bd@[44.50.32.7]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 9 Sep 1997 20:18:22 -0500
To: "Suresh Mali" <smalifreebsd@hotmail.com>
From: Carl Fongheiser <cmf@netins.net>
Subject: Re: Fwd: Posix thread support
Cc: freebsd-hackers@freebsd.org
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>>
>>Hi,
>>
>>I want to find out is the posix thread in FreeBSD-2.2.2. REALESE is
>>stable?
>>
>>Are all libraries are thread safe?

I'd be surprised if *all* the libraries are thread safe.

>>If yes then
>>
>>cd /usr/src/lib/libc_r;  make all && make install
>>
>>will Install all corect thread safe libraries or anything else
>required?
>>
>>Is pthread packege 100 % posix thread complient or anything missing?

No, it's not 100% compliant.  Some gaps:

	sched_yield() doesn't exist.  It's there under the wrong name,
	though;  it's called pthread_yield().

	The static initializer macros (PTHREAD_MUTEX_INITIALIZER,
	PTHREAD_COND_INTIALIZER, etc.) aren't in the public include
	file;  they're squirreled away in
	/usr/src/lib/libc_r/uthread/pthread_private.h

Carl Fongheiser
cmf@netins.net