🚀 go-pugleaf

In article <41hubn$o3c@sundog.tiac.net>, williams@tiac.net says...
>
>tzs@u.washington.edu (Tim Smith) wrote:
>>
>>Basically, optimal scheduling requires taking into account the *global*
>>state of the system.  Cooperative systems make each process, which only
>>knows the *local* state of the system, make scheduling decisions. 
>>
>
>Well put!  As I have said before, cooperative systems make sense in
>certain circumstances.  In the terms you've used above these cercumstances
>are when the local state of the system for each process in the system
>is known to each other process in the system.
>
>Cooperative systems do not work well in heterogenious situations.  The
>programmer has to have complete control of the machine in order to
>make cooperative systems work.

The *real* reason cooperative systems fail is because it is almost 
impossible to do development in an environment where othe people
have to do production work!  And, eventually, even if you've had
a private system to do development you must eventually cut over into
a real production environment which is *almost* guaranteed to be 
broken by that cut over.

Ask Novel developers...which seems to have been overlooked as a cooperative
system by most of the posters in the thread.

>
>-- 
>Sphere.
>
>Find a Linux/GNU Group for you: http://www.tiac.net/users/williams/lugnuts/
>Buy Free UNIX!
>Microsoft is prohibited from examining any packet containing data
>originating on any machine which I am using. (Not that I can stop them.)
>
>