Path: utzoo!mnetor!uunet!cbmvax!rutgers!sri-spam!ames!oliveb!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga
Subject: Re: UNIX on the Amiga
Message-ID: <41976@sun.uucp>
Date: 15 Feb 88 20:35:09 GMT
References: <6836@agate.BERKELEY.EDU> <1869@leo.UUCP> <2836@bloom-beacon.MIT.EDU> <619@ncrcce.StPaul.NCR.COM> <647@nuchat.UUCP>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 19

In article <647@nuchat.UUCP> peter@nuchat.UUCP (Peter da Silva) writes:
> It still wouldn't be as reliable as a plain vanilla UNIX implementation, 'cos
> of all the shared memory segments... but hopefully you could blow the AmigaDOS
> emulation out of the water and get back to plain UNIX if you did get a guru.

Good point Peter, I should be possible to create a virtual memory space that
duplicated the existing Amiga memory space. Some fooling of the kickstart into
believing that there was only 'nK' of memory where n >= 512 might be necessary.
The exception handlers (the fastest way to the big G) would of course be 
handled by UNIX and they could pop you into a UNIX process that was debugging
the AmigaDOS memory image. One bit of subterfuge that may be required would
be a hook into the UNIX process scheduler that would give the AmigaDOS process
higher priority (so it could run when it wanted to and act like a 'real' 
Amiga). Anyone besides me that would rather see a Memory protected, virtual
address space AmigaDOS that can run 'old fashioned' in a separate Task?

--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.