Path: utzoo!attcan!uunet!samsung!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!husc6!spdcc!xylogics!world!madd
From: madd@world.std.com (jim frost)
Newsgroups: comp.os.minix
Subject: Re: MINIX for the Macintosh
Message-ID: <1989Nov21.162536.2690@world.std.com>
Date: 21 Nov 89 16:25:36 GMT
References: <2326@draken.nada.kth.se> <1989Nov20.232801.23983@ux1.cso.uiuc.edu>
Organization: Software Tool & Die
Lines: 38

Excuse me if this has been talked about before, since I missed it, but
I'm terribly interested in MacMINIX.

What is the minimum hardware configuration that MacMINIX will work
with?  By this I mean memory, MacOS version (you said it ran as a Mac
application, right?) etc.  I remember that you said you need a hard
disk, but this is only one possible limitation.

What compiler are you using for MacMINIX?  Is one supplied?  Can gcc
work with it?

How do you support disks (raw devices?  through MacOS calls?  as a
MacOS file with a filesystem inside it?)  What about periferal support
(printer, modem, etc)?  I'm more interested in the "how" than the
"do", since if I get the thing I'm going to hack the hell out of it,
adding whatever I need, but I'm interested in how you are currently
handling such things.

How do you support the terminal?  I assume you just open a Mac window
and use it as a terminal.

What kind of limitations are there on user program size?  I assume
there aren't any other than physical memory (as with the ST version,
right?) but I'd like to know for sure.

If it's indeed running as a MacOS application, how well does it deal
with multifinder and minifinder?

I'm really curious.  I've been thinking about buying a machine to do
OS work on and was considering building a version of MINIX that did VM
on a 386 machine (64k limits are, well, limiting), but I have a Mac
already so news of a Mac version really excites me.

Thanks for any replies,

jim frost
software tool & die
madd@std.com