Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Mon, 23 Apr 2001 20:31:41 -0400 From: Christopher Faylor To: Robert Collins Cc: John Fortin , cygwin-developers AT cygwin DOT com Subject: Re: Looking for something to work on... Message-ID: <20010423203141.A2151@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: Robert Collins , John Fortin , cygwin-developers AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from robert.collins@itdomain.com.au on Tue, Apr 24, 2001 at 10:20:10AM +1000 On Tue, Apr 24, 2001 at 10:20:10AM +1000, Robert Collins wrote: >> I guess we should move this discussion to cygwin-developers... >> >> John was asking for something interesting to do. He suggested POSIX >> IPC stuff, which I (possibly erroneously) assumed was the same as what >> cygipc provided. > >It is. See http://www.opengroup.org/onlinepubs/7908799/xsh/ipc.html - >it's essential sysV IPC. To some extent these are equivalent to mmap and >the like, but I don't think mmap is cross process-persistent in cygwin >(And I don't know if it's meant to be). We could of course implement shm >with disk backing not VM backing, but that might cause issues with Gb >allocs :] I could actually donate some Windows code that I wrote a few years ago to emulate sys v semaphores. It wasn't complete but it might be useful as either a starting point or a laughing point. cgf