Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!ucbcad!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re: MINIX port to A1000
Message-ID: <8711050807.AA03297@cory.Berkeley.EDU>
Date: Thu, 5-Nov-87 03:07:39 EST
Article-I.D.: cory.8711050807.AA03297
Posted: Thu Nov  5 03:07:39 1987
Date-Received: Sat, 7-Nov-87 19:28:29 EST
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 25

>     Also, I am considering building the MINIX kernel into the WCS of the
>1000.  If I have any thoughts of being so ambitious, I need to know just
>what makes a kickstart disk tick.  Anybody out there in net land know the
>kickstart format?
>     Another possibility is running MINIX as a task under AmigaDOS.  This
>would be really neat, but I forsee mega problems with MINIX bumping into
>AmigaDOS.  (i.e. which memory manager really controls the memory, etc.)
>     What it all boils down to is that I am relatively inexperienced with

	AmigaDOS?  The best way to go is to run MINIX on top of the Amiga's
OS.  Specifically, EXEC tasks.  You do not have to bother with DOS or
memory allocation.  In fact, if you are porting the filesystem interface
you'd want to talk directly to the trackdisk.device (i.e. result=
incompatible floppy formats).  There are ways to get around all the 
"limitations" of the EXEC in a tightly controlled enviroment such as an
overlayed operating system.  Memory?  If you can't integrate allocation with
the Amiga's allocation, simply allocate a whole bunch and say that's the
memory MINIX has to play with.

	What you need to do this is the entire manual set, excluding the
hardware manual.... you really need to know how to program on an Amiga.
For instance, do you know how software interrupts (task exceptions, signal
generated exceptions, etc) work? 

					-Matt