From owner-freebsd-standards@FreeBSD.ORG Sat Oct 16 19:05:37 2004 Return-Path: Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C843516A4CE for ; Sat, 16 Oct 2004 19:05:37 +0000 (GMT) Received: from VARK.MIT.EDU (VARK.MIT.EDU [18.95.3.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7744A43D39 for ; Sat, 16 Oct 2004 19:05:37 +0000 (GMT) (envelope-from das@FreeBSD.ORG) Received: from VARK.MIT.EDU (localhost [127.0.0.1]) by VARK.MIT.EDU (8.13.1/8.12.10) with ESMTP id i9GJ5b0O008218; Sat, 16 Oct 2004 15:05:37 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.MIT.EDU (8.13.1/8.12.10/Submit) id i9GJ5b4a008217; Sat, 16 Oct 2004 15:05:37 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Date: Sat, 16 Oct 2004 15:05:37 -0400 From: David Schultz To: "Kamal R. Prasad" Message-ID: <20041016190536.GA77093@VARK.MIT.EDU> Mail-Followup-To: "Kamal R. Prasad" , Garance A Drosihn , freebsd-standards@FreeBSD.ORG References: <416EA82F.6060102@kprasad.org> <416F28F9.107@kprasad.org> <20041015021636.GA65967@VARK.MIT.EDU> <417167DD.2010101@kprasad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <417167DD.2010101@kprasad.org> cc: freebsd-standards@FreeBSD.ORG cc: Garance A Drosihn Subject: Re: ps command X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Oct 2004 19:05:37 -0000 On Sat, Oct 16, 2004, Kamal R. Prasad wrote: > >Yes, there's a list at > > > > http://www.freebsd.org/projects/c99/index.html > > > >It isn't up-to-date, but it should give you a pretty good idea of > >what needs to be done. > > > > > I see one to-do to make code thread-safe. Im not sure and would like > someone to elaborate on that. Besides that, I am looking for some > generic to-do stuff inside the kernel [or at most libc] but doesn't > require special hardware. . POSIX defines all standard functions to be thread-safe, except ones on the list here: http://www.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_09.html I don't know of any routines offhand that are required to be thread-safe but aren't already. You'd have to poke around and see what you could find.