Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!rochester!udel!mmdf From: rminnich%super.org@UDEL.EDU Newsgroups: comp.sys.amiga Subject: Re: OS/2 vs. Pournelle Message-ID: <4431@louie.udel.EDU> Date: 3 Oct 88 22:23:16 GMT Sender: mmdf@udel.EDU Lines: 31 Received: from CUNYVM by CUNYVM.BITNET (Mailer X2.00) with BSMTP id 5349; Sun, 02 Oct 88 01:01:21 EDT Received: from UDEL.EDU by CUNYVM.CUNY.EDU (IBM VM SMTP R1.1) with TCP; Sun, 02 Oct 88 01:01:15 EDT Received: from Louie.UDEL.EDU by Louie.UDEL.EDU id aa20178; 1 Oct 88 0:15 EDT Received: from USENET by Louie.UDEL.EDU id aa20176; 1 Oct 88 0:14 EDT From: Ronald G Minnich Subject: Re: OS/2 vs. Pournelle Message-ID: <800@super.ORG> Date: 30 Sep 88 13:37:59 GMT Organization: Supercomputing Research Center, Lanham, MD To: amiga-relay@UDEL.EDU Sender: amiga-relay-request@UDEL.EDU in article <5384@fluke.COM> kurt@tc.fluke.COM (Kurt Guntheroth) writes: >Here's a question I want answered...Do PS/2 (OS/2) machines have memory >protection? I don't mean software segments. I mean hardware protection. AN even more interesting question. (Yes, OS/2 has protection btw. But that is only one of the bomb-producing issues. Unix V6 had protection and it crashed *often*- that's where i cut my kernel teeth). But how does the message passing work? Is it 'copy the message' or 'map it into your space'? If it is the latter, where do they get mapped in? To the same virtual address per process? Or to a different virtual address? If to a different virtual address, then all the pointers in the message are invalid. If to the same, how do they guarantee that there is not something already there? On the amiga if it ever does got memory management it is done via the equivalent of 'map it in'. Since all processes live in a large linear address space it will work right even with memory management- it will still be VERY efficient. Is OS/2 copy or map in? Anybody know? ron