Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Wed, 28 Mar 2001 10:22:58 +0200
From: Corinna Vinschen <vinschen AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: fifos and named pipes
Message-ID: <20010328102258.T16622@cygbert.vinschen.de>
Reply-To: Corinna Vinschen <cygwin-developers AT cygwin DOT com>
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <EA18B9FA0FE4194AA2B4CDB91F73C0EF02E2B8 AT itdomain002 DOT itdomain DOT net DOT au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <EA18B9FA0FE4194AA2B4CDB91F73C0EF02E2B8@itdomain002.itdomain.net.au>; from robert.collins@itdomain.com.au on Wed, Mar 28, 2001 at 12:21:21PM +1000

On Wed, Mar 28, 2001 at 12:21:21PM +1000, Robert Collins wrote:
> Ok. Any known problems with memory mapped files on 95? I'll just store
> struct in the actual disk after the magic number, and memory map to that
> file. Access control to the file will be handled by the OS as per usual.

Memory mapping on 9x/ME...

- use only basic shared access modes
- don't play with copy-on-write (Chris and I, we both have gray hair
  because of that)
- don't force a fixed memory address (aka mmap(...,MAP_FIXED,...))

Everything else should work... mostly.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.