Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ziploc!eps
From: eps@toaster.SFSU.EDU (Eric P. Scott)
Newsgroups: comp.sys.next
Subject: Re: SYSV IPC
Summary: do it yourself?
Keywords: interprocess communication
Message-ID: <228@toaster.SFSU.EDU>
Date: 9 Jan 90 11:11:43 GMT
References: <325@ge1cbx.UUCP>
Reply-To: eps@cs.SFSU.EDU (Eric P. Scott)
Organization: San Francisco State University
Lines: 15

In article <325@ge1cbx.UUCP> gerald@ge1cbx.UUCP (Gerald Aden) writes:
>Does anyone know whether or not NeXT is planning on adding SYSV interface
>extensions (i.e.  message queues, shared memory, semaphores) to MACH?

(I don't know what NeXT's plans are in this regard)

It shouldn't be that hard to develop a compatibility library for
those (at least you're not asking for STREAMS--whew!).  The trick
is to make sure things get cleaned up properly if a process dies
unexpectedly... (also reentrancy for multithreaded applications)

"Doing it right" probably means something you can feed to
kern_loader, but I'd try a user-mode approach first.

					-=EPS=-