From owner-freebsd-current Mon Sep 15 04:14:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA22100 for current-outgoing; Mon, 15 Sep 1997 04:14:08 -0700 (PDT) Received: from freebsd1.cimlogic.com.au ([203.36.2.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA22090 for ; Mon, 15 Sep 1997 04:13:58 -0700 (PDT) Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.8.5/8.8.5) id VAA02183; Mon, 15 Sep 1997 21:14:39 GMT From: John Birrell Message-Id: <199709152114.VAA02183@freebsd1.cimlogic.com.au> Subject: Re: Thread safe libc In-Reply-To: <341C8C87.2781E494@whistle.com> from Julian Elischer at "Sep 14, 97 06:16:55 pm" To: julian@whistle.com (Julian Elischer) Date: Mon, 15 Sep 1997 21:14:38 +0000 (GMT) Cc: ianh@saturn-tech.com, freebsd-current@FreeBSD.ORG, johnbi@rdd.neca.nec.com.au X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Julian Elischer wrote: > discuss this with john birrel. > > he's hiding at the moment at: > johnbi@rdd.neca.nec.com.au > > he did most of what's been done so far.. > he's likely to say > "be my guest" as far as doing more work on this goes, as he's very busy. I've only just put my machine back on line after spending the last 4 months doing battle with a nasty mix of OS9, WinNT and custom radio hardware. As has been said on this list before (often by core members), contributions that take us toward a re-entrant and thread-safe libc/libc_r are most welcome. > > julian > > Ian Hungerford wrote: > > > > In my recent browsings through the -stable and -current trees, I have > > found (to my immense dismay) that libc is not really thread safe at all. > > It appears at first glance that stdio & malloc are pretty much covered, > > but string & net appear to be untouched. I'm willing to do the work here > > (or assist if somebody's already at it). So if there is a somebody, speak > > up. :) The net functions require a lot of work because they need to be re-coded in *_r() style, with the traditional functions that use the static variables becoming wrappers around these. Work on the net part of libc should be offered to Garrett Wollman for review, since he holds the networking crown for FreeBSD. > > > > Also, I run a -stable system, and I can't see my self using -current until > > I get another box - what are the chances of any patches to -stable libc > > sliding in a smooth and orderly way into -current? I'll upgrade if I must > > (threads are somewhat necessary for my current project), but I'd much > > rather stick with -stable for now. If you had enough disk space, you could run *both* -current and -stable. > > > > --- > > Ian > Regards, -- John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137