> What is the current state of libc's thread safeness? is there any plans to
> make 1.5 threadsafe? or even any project going on to do so? does the
> kernel suport threads well enuf for a thread safe libc and thread
> implementation to be included in the base yet? Could the unproven-threads
> be intergrated into libc to at least result in a good starting base for
> thread suport? what other things than libc would be effected by threads?

I don't know what the plan is, but some of our developers are using 
the Netscape Portable Runtime library, NSPR for thread stuff.
It looks fairly clean, and works across a bunch of platforms, using
pthreads when appropriate.