🚀 go-pugleaf

In article <1992Sep1.211133.21384@news.lrz-muenchen.de> jolly@next2.cis.uni-muenchen.de () writes:
>I think it is very useful to know, that the NeXT-Mach Kernel
>does not support more than 2oo threads !
[..munched..]
>I don t know if 3.o solves that kernel-bug. ( using 2.1 )

This is not a bug.  All operating system kernels have resource limits. Congrats,
You've discovered one of mach's.  There's more than one way to kill a kernel by
exceeding its limits, many I'm sure will remember that oldie but goodie
"while(1) fork() ;".  You have to program around these limits, you can't just
claim its a bug and push it onto someone elses plate.  I don't remember
which header file contains a macro indicating the max number of threads per
task, but I do know it exists ( anyone care to jump in with that info? ).

>Post Post Scriptum : I think that NeXT should not publish files, which
>		     will panic the system after inserting only one
>		     character. ( The only thing you have to do is to
>		     insert a "2" in front of the "15" in the NeXT 
>		     Operating System thread-example ).

And files that will hang the system if 17 characters are inserted!! ( See
above )  Is it to late to have NeXT wipe the Examples directory clean in
3.0!!!  And we must get rid of that nasty compiler, it could be twisted
into a tool of system destruction! :-) :-) :-)

-=Chris

-- 
Christopher D. Audley                 Internet: audley@jhunix.hcf.jhu.edu
Elec & Comp Engineering                      -= NeXTmail Welcome =-
The Johns Hopkins University          Phone: (410)889-3639