cvs commit: doc/en_US.ISO8859-1/articles/contributors contrib.additional.sgml contrib.committers.sgml doc/en_US.ISO8859-1/share/sgml authors.ent doc/share/pgpkeys pgpkeys-developers.sgml pgpkeys.ent t

2010-07-17 Thread Tijl Coosemans
tijl2010-07-17 18:32:42 UTC FreeBSD doc repository (src committer) Modified files: en_US.ISO8859-1/articles/contributors contrib.additional.sgml contrib.committers.sgml en_US.ISO8859-1/share/sgml authors.ent share/pgpkeys

Re: cvs commit: src/sys/kern kern_thr.c syscalls.master src/sys/sys thr.h

2007-08-18 Thread Tijl Coosemans
gt;>> I realize what it's for, and I don't agree that it belongs in the >>> tree. There are other forms of interprocess communication, pipes, >>> sockets, even msg queues. I'm sure you can find a few ways to send >>> a message to a process to say "

Re: cvs commit: src/sys/kern kern_thr.c syscalls.master src/sys/sys

2007-08-19 Thread Tijl Coosemans
On Sunday 19 August 2007 16:44:09 Daniel Eischen wrote: > Thread id's (as visible to an application) are not required to be > something that is known by the kernel. They certainly are not in > libkse and libc_r, and I don't think they are in libthr either. > This API won't work with libkse (or lib

Re: cvs commit: src/sys/kern kern_thr.c syscalls.master src/sys/sys

2007-08-19 Thread Tijl Coosemans
On Sunday 19 August 2007 16:53:13 Daniel Eischen wrote: > On Sun, 19 Aug 2007, Alexandre Julliard wrote: >> Daniel Eischen <[EMAIL PROTECTED]> writes: >>> FreeBSD as well as Solaris and Linux (it looks like Linux only >>> allows a thread group to be signaled) have gotten along without >>> this API,