Path: utzoo!utgpu!watserv1!watmath!att!att!pacbell.com!ucsd!usc!wuarchive!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!metro!natmlab.dap.csiro.au!ditsydh.syd.dit.CSIRO.AU!evans
From: evans@syd.dit.CSIRO.AU (Bruce.Evans)
Newsgroups: comp.os.minix
Subject: Re: Minix 68k queries
Message-ID: <1990Oct23.071519.19409@syd.dit.CSIRO.AU>
Date: 23 Oct 90 07:15:19 GMT
References: <1990Oct17.164053.27568@eecs.wsu.edu>
Organization: CSIRO Division of Info Tech, Sydney, Australia
Lines: 20

In article <1990Oct17.164053.27568@eecs.wsu.edu> akarkare@eecs.wsu.edu (Ashish Karkare) writes:
>1. Is it possible to make the Minix kernel ROMable? This might allow us to
>play around with diskless versions of Minix.

No reason why not. At worst you can copy the whole thing to RAM. Relocation
may be slightly harder for the 68K.

>2. The Atari ST minix requires 1k per task as opposed to the 512 bytes of
>PC Minix. Why is this so ?

1k for task stacks? Tasks themselves mostly take much more. The stack sizes
are mostly 512 for Minix-ST and 256 for Minix-PC. The 68000 has larger pointers
than the 8086, so more stack is required.

>3. Does Minix require a physically (logically) contiguous memory? 

No, provided there are contiguous blocks large enough to hold processes.
Disconnected memory leads to more wastage from fragmentation.
-- 
Bruce Evans		evans@syd.dit.csiro.au