Xref: utzoo comp.sys.atari.st:17138 comp.os.minix:6085
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!sdcsvax!ucsdhub!hp-sdd!ncr-sd!crash!pnet01!jca
From: jca@pnet01.cts.com (John C. Archambeau)
Newsgroups: comp.sys.atari.st,comp.os.minix
Subject: Minix, ST, and forking...
Message-ID: <4385@crash.cts.com>
Date: 15 Jun 89 00:36:21 GMT
Sender: news@crash.cts.com
Organization: People-Net [pnet01], El Cajon CA
Lines: 27

I recently was on bugs.nosc.mil looking for the problems that I saw in the
file 'subjects' dealihng with ST and the Minix system call fork.
Unfortunately, the only message in the archives on bugs.nosc.mil with that
subject header wasn't about the problems with ST Minix and memory management,
but rather about implementing swapping.
 
I have heard from a somewhat questionable grapevine that ST Minix has a
problem with forking processes and the problem is attributed to the Blitter
and/or the fact the ST doesn't use a typical MC680x0 MMU, but Atari's custom
chip set.  Were these problems corrected (if they existed) or just swept under
the metaphorical rug?

What I want to know is the following;
 
1. Are there problems with ST Minix memory management (i.e. fork/exec)?
2. What are the exact differences between IBM and ST Minix on a memory
   management level?  

 /*--------------------------------------------------------------------------*
  * That's not an operating system, this is an operating system!
  *--------------------------------------------------------------------------*
  * UUCP: {nosc ucsd hplabs!hp-sdd}!crash!pnet01!jca
  * APRA: crash!pnet01!jca@nosc.mil
  * INET: jca@pnet01.cts.com
  *--------------------------------------------------------------------------*/
  
#include <disclaimer.h>