Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mit-eddie!uw-beaver!zephyr.ens.tek.com!gvgpsa!treehouse!andyp
From: andyp@treehouse.UUCP (Andy Peterman)
Newsgroups: comp.sys.mac.misc
Subject: Re: Mac OS versus A/UX, Who runs under who?
Message-ID: <627@treehouse.UUCP>
Date: 4 Nov 90 18:34:23 GMT
References: <27337f93-fe.1comp.sys.mac.misc-1@tronsbox.xei.com> <3818@idunno.Princeton.EDU> <{'!^2|*@rpi.edu>
Organization: The Tree House
Lines: 21

In article <{'!^2|*@rpi.edu> Garance_Drosehn@mts.rpi.edu (Garance Drosehn) writes:
>I thought that A/UX, when it's running, is the operating system in control 
>of the machine.  The Mac OS, if it is running with A/UX, runs as a process 
>under A/UX.  As such, it would not be correct to say that A/UX is running 
>on top of the Mac OS.  True?  False?  True on somedays but False on others?

True all of the time.  When the A/UX kernel starts up, it is completely
in charge of the machine.  It then starts up the MacOS as a process
along with MultiFinder and an 8 meg virtual memory space.  The MacOS then
brings up Finder as its shell.  As such, anything running under the
MacOS is treated as just another process.  In fact, you can totally bomb
a program and A/UX keeps running, a VERY nice feature.  After the
program bombs, you can sometimes recover within the MacOS, or "restart",
which simply kills the MacOS process and logs you out, all without
affecting any other A/UX process, except for stealing a lot of processor
time.

-- 
Andy Peterman                       |   Opinions expressed
treehouse!andyp@gvgpsa.gvg.tek.com  | are definitely those of
(916) 273-4569                      |      my employer!