Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!sol.ctr.columbia.edu!emory!gatech!udel!rochester!pt.cs.cmu.edu!a.gp.cs.cmu.edu!cmaeda
From: cmaeda@a.gp.cs.cmu.edu (Christopher Maeda)
Newsgroups: comp.sys.next
Subject: shared memory on NeXT
Summary: don't be a System V loser
Message-ID: <12159@pt.cs.cmu.edu>
Date: 28 Feb 91 23:21:34 GMT
Organization: Carnegie-Mellon University, CS/RI
Lines: 17

Why not just rewrite your code to use ports and messages?  A mach
message (within a single host) is implemented as a piece of shared
memory anyway.  You don't need to mess with semaphores since the OS
does the synchronization for you when it delivers the message.  You
also get network transparency for free.

I imagine the reason the vm code doesn't let arbitrary processes share
pieces of memory is that you are supposed to use ports and messages
for this sort of thing.



-- 
Chris Maeda, CMU CS                     |Mail:	cmaeda@cs.cmu.edu
Yow!  I find I enjoy netnews more after |UUCP:  fuck if I know
having a couple of twinkies and a coke. |(si:halt "boot
Am I a Unix Weenie yet?                 |")