From owner-freebsd-current Sun Sep 14 17:01:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA12401 for current-outgoing; Sun, 14 Sep 1997 17:01:55 -0700 (PDT) Received: from hobbes.saturn-tech.com (ianh@drussell.internode.net [198.161.228.154]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA12391 for ; Sun, 14 Sep 1997 17:01:51 -0700 (PDT) Received: from localhost (ianh@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id SAA20557 for ; Sun, 14 Sep 1997 18:01:40 -0600 (MDT) Date: Sun, 14 Sep 1997 18:01:40 -0600 (MDT) From: Ian Hungerford To: freebsd-current@freebsd.org Subject: Thread safe libc Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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. :) 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. --- Ian