Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!panews.awdpa.ibm.com!ibmpa.awdpa.ibm.com!webb
From: webb@ibmpa.awdpa.ibm.com (Bill Webb)
Newsgroups: comp.os.mach
Subject: Re: shared memory in Mach?  (Esp. for NeXT)
Message-ID: <1991Feb21.143442@ibmpa.awdpa.ibm.com>
Date: 21 Feb 91 22:34:42 GMT
References: <1991Feb21.072121.24132@rfengr.com>
Sender: news@ibmpa.awdpa.ibm.com (news id)
Reply-To: webb@ibmpa.awdpa.ibm.com (Bill Webb)
Organization: IBM AWD Paloalto
Lines: 21

In article <1991Feb21.072121.24132@rfengr.com>, briand@rfengr.com (Brian Dear) writes:
|> 
|> Forgive me if this is a stupid question.  Here goes:
|> 
|> My first exposure to Mach is via the NeXT machine.  One thing I was
|> disappointed to discover was that with NeXT's OS, there is no support
|> for "shared memory" operations such as System V's shmget(), shmat(),
|> and shmdt().
|>  
|> Does anyone know if a simple way to implement the equivalent of
|> AT&T System V shared memory in a Mach-style environment?  ...
|> ...
|> Brian Dear                  brian@coconut.com          Coconut Computing, Inc.

The simplest way of getting this would be to get OSF/1 which is based on
Mach and has the shm* facilities.

----------------------------------------------------------------
The above views are my own, not necessarily those of my employer.
Bill Webb (IBM AWD Palo Alto, Ca.), (415) 855-4457.
UUCP: ...!uunet!ibmsupt!webb INTERNET: webb@ibminet.awdpa.ibm.com


Brought to you by Super Global Mega Corp .com