Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!snorkelwacker.mit.edu!ira.uka.de!fauern!opal!tmpmbx!scuzzy!src
From: src@scuzzy.in-berlin.de (Heiko Blume)
Newsgroups: comp.unix.sysv386
Subject: Re: binary Mach distribution for 386
Message-ID: <1991Jan07.152536.28530@scuzzy.in-berlin.de>
Date: 7 Jan 91 15:25:36 GMT
References: <13963@uswat.UUCP> <1991Jan4.140341.11874@granite.cr.bull.com> <1991Jan05.021138.17495@scuzzy.in-berlin.de> <1991Jan5.180851.24
Organization: Contributed Software
Lines: 22

shore@mtxinu.COM (Melinda Shore) writes:

>In article <1991Jan05.021138.17495@scuzzy.in-berlin.de> I wrote:
>>kittlitz@granite.cr.bull.com (Edward N. Kittlitz) writes:
>>>Also, there is apparently no binary compatability
>>>support (ABI?) for System V.3.
>>
>>nothing stops us from emulating that too.

>This distribution is based on Mach 2.5, which has a monolithic kernel.
>Filtering before execution might be a possibility, but Mach doesn't
>support execution out of multiple 386 segments.

what a pitty, will Mach 3.0 have the main "kernel" components (except
the message passing et al) in seperate processes? i always considered
this one of the main advantages. btw: the uni i'm at has a message
passing system called AX, that 'knows' ms-dos, qnx and sorta sys v.
-- 
      Heiko Blume <-+-> src@scuzzy.in-berlin.de <-+-> (+49 30) 691 88 93
                    public source archive [HST V.42bis]:
        scuzzy Any ACU,f 38400 6919520 gin:--gin: nuucp sword: nuucp
                     uucp scuzzy!/src/README /your/home