Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!labrea!jade!eris!spencer
From: spencer@eris.UUCP
Newsgroups: comp.sys.amiga
Subject: MMU operations (was Re: resource tracking problem)
Message-ID: <5118@jade.BERKELEY.EDU>
Date: Thu, 17-Sep-87 02:38:25 EDT
Article-I.D.: jade.5118
Posted: Thu Sep 17 02:38:25 1987
Date-Received: Sat, 19-Sep-87 07:17:33 EDT
Sender: usenet@jade.BERKELEY.EDU
Reply-To: spencer@eris.BERKELEY.EDU (Randy Spencer)
Organization: University of California, Berkeley
Lines: 50

In article <81@ur-tut.UUCP>  (Davide P. Cervone) writes:
>
>I have a concern that doesn't seem to have been addressed yet in the "kill
>any process" suggestions.

  Basically he says "If all we do is free up the memory of a killed
  process, what happens to:

     Memory that has been sent to another process as a message,

     Other process that allocate memory because of the killed process:
        Windows that I opened
        The space the screen open in its list
        The LayerInfo structure

     Also processes could be locked and never exit:
        The console process that talks to my window
        The serial device, which would never let others use it

>
>In an environment where process share their resources in so many ways, I 
>really worry about cleaning up after a process without some knowledge of what
>that process was doing.  I hope someone finds a way to do it, though.
>
>Davide P. Cervone

Now, I can understand why so many programmers are talking about an Exec
that tracks resources, since it would save so much programming time, but
as David points out, I don't think that there is alot that can be done 
about it at this point.  Especially with Commodore not wanting to mess
with already developed software, and with a developer base that has only
recently stopped complaining about an OS that is changing on them all
the time.

Where I think all this discussion could lead is into how to re-write the
OS to support an MMU on the 2000 (we do have an MMU slot you know).  We
already have problems with the OS, in that the whole message-passing
environment *relys* on everybody getting to everything.  

Since it does rely on it, there will have to be some sort of re-write
when the MMU board is released.  So, what do we need to do to get the OS
to work in a protected memory environment?
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Randy Spencer      P.O. Box 4542   Berkeley  CA  94704        (415)284-4740 
                         I N F I N I T Y                 BBS: (415)283-5469
Now working for          |||||||||||::::... . .                    BUD-LINX
But in no way            |||||||||||||||::::.. .. .
Officially representing  ||||||||||||:::::... ..    ....ucbvax!mica!spencer
                         s o f t w a r e          spencer@mica.berkeley.edu
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-