Mail Archives: cygwin-developers/2001/10/24/01:25:18

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: <>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: Need name and functionality suggestions for a new utility
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Date: Wed, 24 Oct 2001 15:33:15 +1000
Message-ID: <>
Thread-Topic: Need name and functionality suggestions for a new utility
Thread-Index: AcFcTEcpJx3J8MBjQ4GEhhmCF5SwWwAAAmHgAAA3nBA=
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-developers AT cygwin DOT com>
X-MIME-Autoconverted: from quoted-printable to 8bit by id f9O5PHv05833

> > I don't think I want to go that crazy.  This is just for 
> > cygwin objects.
> > Theoretically, the whole mount table will look different so mmap
> > objects, at least, will refer to different paths anyway.
> Ahh, touch /t
> run prog that mmaps to /t
> will conflict unless the named objects are created using 
> win32 paths as
> their basis. And for canonical behaviour using the unix path 
> makes sense
> to me.

I should mention why I'm concerned:

The first thing that will happen when this utility is available is that
anyone having multiple-cygwin-cross-comple-vendor-tools-issues (remember
the list recently) will try it. If it's suitable for running an isolated
test suite, but not for production side by side use, I can just imagine
the traffic volume.


- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019