Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!hub!castor!stoms
From: stoms@castor.ncgia.ucsb.edu (David Stoms)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Why not Mach as version 8.0
Message-ID: <4260@hub.UUCP>
Date: 11 Mar 90 00:14:23 GMT
References: <39127@apple.Apple.COM> <1236@swbatl.sbc.com>
Sender: news@hub.UUCP
Reply-To: stoms@castor.ncgia.ucsb.edu (David Stoms)
Organization: U. C. Santa Barbara, Geography Department
Lines: 17

In article <1236@swbatl.sbc.com> gilstrap@swbatl.UUCP (Brian Gilstrap - UCI - 5-3929) writes:
>Okay, perhaps someone can answer me this question:  why not use an
>implementation of Mach as verrsion 8.0 of the MacOS?  It would seem that you
>could preserve the shared memory areas via Mach's shared virtual memory through
>VM inheritance (e.g. don't copy-on-write but inherit a shared chunk of VM).
>This would allow the large majority of Mac programs which do twiddly things
>in the system heap and such to still run correctly.

First of all, Apple is never going to use any implementation of Unix in their
current Mac platform for a number of reasons. Natually, Apple wont license a
Unix from anyone and they wont want to rewrite the File Mgr again without a
_VERY_ good reason. If Apple did decide to convert the File Mgr to un*x,
it would be almost impossible to keep all the current programs compatable. Just
the '/' instead of ':' would screw a few programs up and what about file types?.

BUT, I would like to hear more about "Mach's shared virtual memory" though.
Sounds interesting.