Benny Pedersen wrote:
> > I believe that MorphOS solves this problem, because Memory protection
> > is inside MorphOS (as said on www.morphos.de).
> then why not use mmu.library now on 68k ?
mmu.library could protect memory between tasks, but the way the
AmigaOS works relies on different tasks looking at structures passed
between each other. For memory protecting OS's, the way round this is
to pass copies of all inter-task structures, rather than pointers to
structures. This is slower and requires a more well-defined
Kernel/User space model, but allows lots of other clever stuff like
remote multiprocessing etc.
In other words, the basic AmigaOS could not operate with simple memory
protection in its current form. With non-trivial changes to the OS and
API it could be made to work in a similar way, but almost all software
would have to be re-written to some extent.
Regards,
Ian
===
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
