Path: utzoo!attcan!uunet!lll-winken!csd4.milw.wisc.edu!mailrus!uflorida!gatech!udel!mmdf
From: 451061%UOTTAWA.BITNET@cornellc.cit.cornell.edu (Valentin Pepelea)
Newsgroups: comp.sys.amiga
Subject: Re: Apple System 7.0 [ and some 1.4 suggestions ]
Message-ID: <15596@louie.udel.EDU>
Date: 16 May 89 20:14:08 GMT
Sender: mmdf@udel.EDU
Lines: 24

Fred Gilham <gilham@polya.stanford.edu> in Message-ID: <9160@polya.Stanford.EDU>
> I used Forbid() and Permit() to allow me to start up a task where
> things weren't quite ready for it.  The parent simply did a Forbid()
> until it had finished setting things up.  This seemed like a good use
> of Forbid() to me.

A simple solution to this would be for Commodore to create a few new system
semaphores for V1.4 of the operating system. When you want to modify the
list of task structures, you would simply grab the TaskList semaphore until
you complete you operation on the list. Thus when a task switch is about to
occur, the system would refuse to perform it. Effectively multi-tasking is
disabled, but now the system knows why. When a page fault occurs, the page
fault manager now knows wether it is safe to perform a swap or not.

This is the way things should be. This is not a hack nor a cludge. This is
the way you will see things done a future release of the OS. (Boy, I sure am
confident about those things eh?)

_________________________________________________________________________
"An  operating  system  without         Name:   Valentin Pepelea
 virtual memory is an operating         Phonet:
 system without virtue."                Bitnet: 451061@Uottawa.bitnet
                                        Usenet: Use cunyvm.cuny.edu gate
         - Ancient Inca Proverb         Planet: 451061@acadvm1.UOttawa.CA