------------ Thread properties ----------- 1/ Multiple independent 'threads of control' within a single process at user level. The most basic quality of threads.

2/ Ability to simultaneously schedule two threads over separate Processors.

3/ Inability of one thread to block aother thread unless they are intentionally synchronising.

4/ All threads see the same address space (exactly).

5/ All threads share the same file resources.

6/ (contentious) multiple theads should be bound to within the resource limits of the single process.

7/ Some well documeted scheme exists for handling signals and othe rasync events.

8/ Exit/shutdown protocol is well defined.

9/ there exists a set of primatives that allow threads to influence the in-process scheduling between themselves.

10/ your ideas here. Note, you an also suggest that I remove an idea.

It is notable that we already support Linux kernel threads on FreeBSD better than we support a native threads model. This is because we support the 'clone' system call through our rfork() code, and that is their basis for threading. As is common for this group of people, we have not adopted the Linux approach because it is considered to be 'too simplistic', assigning a separate kernel schedulable process to run each thread.