Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!UOTTAWA.BITNET!451061
From: 451061@UOTTAWA.BITNET (Valentin Pepelea)
Newsgroups: comp.sys.amiga.tech
Subject: Re: MEMF_PHYSICAL?
Message-ID: <8905240034.AA04958@jade.berkeley.edu>
Date: 24 May 89 00:23:16 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 45

Dave Thomas QA <thomas@cbmvax.uucp> writes in Message-ID: <6955@cbmvax.UUCP>

- In article <8905222148.AA05879@jade.berkeley.edu> 451061@UOTTAWA.BITNET
- (Valentin Pepelea) writes:
- > If that happens, simply pop up a
- > requester saying "Task xxx tried to write on memory belonging to task yyy".
- > Then offer gadgets with the following functions:
- >
- > 1. Allow task xxx to overwrite any memory belonging to task yyy.
- > 2. Allow task xxx to overwrite any memory.
- > 3. Kill task xxx.
- > 4. Guru.
-
- Your solution would probably work, but the sheer number of programs which
- do not properly ask for MEMF_PUBLIC would cause this requester to show up
- quite frequently.
- ...
- I don't think having a requester pop up every time I try to pull down a
- menu is going to be an acceptable solution.

Oops, I think I did not make myself clear enough. Let me put it like this:
If a task xxxx tries to access memory belonging to task yyyy, then a request
will pop up displaying "Task xxxx tried to write in task's yyyy memory". A
list of gadgets will offer the following functions:

1. Allow task xxxx to write in task's yyyy memory only this time.
2. Allow task xxxx to write in system memory only this time.
3. Allow task xxxx to write in task's yyyy memory always from now on.
4. Allow task xxxx to write in system memory always from now on.
5. Kill task xxxx.
6. Guru.

Heh! Still 100% backwardly compatible. We should remember that yyyy's memory
is by default readable and only writes are initially inhibited. Furthermore,
we should remember that CBM has already set the proper rules clearly on where
MEMF_PUBLIC is required. Unlike for virtual memory, devellopers would not be
allowed to cry wolf on this one.

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