From owner-freebsd-hackers  Tue Mar 24 09:19:37 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA24164
          for freebsd-hackers-outgoing; Tue, 24 Mar 1998 09:19:37 -0800 (PST)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from misery.sdf.com (misery.sdf.com [204.244.213.32])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA24137
          for <hackers@freebsd.org>; Tue, 24 Mar 1998 09:19:30 -0800 (PST)
          (envelope-from tom@sdf.com)
Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3)
	id 0yHWzP-000558-00; Tue, 24 Mar 1998 08:55:51 -0800
Date: Tue, 24 Mar 1998 08:55:49 -0800 (PST)
From: Tom <tom@sdf.com>
To: Dalibor Sramek <dali@proxima.britcoun.cz>
cc: hackers@FreeBSD.ORG
Subject: Re: Free-BSD threads & IO
In-Reply-To: <Pine.BSF.3.95q.980324095404.3529A-100000@proxima.britcoun.cz>
Message-ID: <Pine.BSF.3.95q.980324085502.19504B-100000@misery.sdf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Tue, 24 Mar 1998, Dalibor Sramek wrote:

> So - is there any explanation for this problem and is thread support OK in
> Free-BSD? I still use 2.2.1 installation.

  There are many bugs in libc_r in 2.2.1.  Most were fixed in 2.2.6, but
signal/alarm handling seems a little funny.

> Thanks
> 
> Dalibor Sramek
> The British Council, Prague Czech Republic

Tom


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