Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Subject: RE: Cygwin: Interoperability Is Important (was Cygwin: Open or Closed System, etc)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Wed, 27 Jun 2001 14:31:09 +1000
Message-ID: <EA18B9FA0FE4194AA2B4CDB91F73C0EF08F0A0@itdomain002.itdomain.net.au>
content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Cygwin: Interoperability Is Important (was Cygwin: Open or Closed System, etc)
Thread-Index: AcD+wR1k68AKfvwoT7+baIpMCzDFHgAAA/lw
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Fred T. Hamster" <fred@gruntose.com>, <cygwin@cygwin.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id AAA28918

> -----Original Message-----
> From: Fred T. Hamster [mailto:fred@gruntose.com]
> Sent: Wednesday, June 27, 2001 2:35 PM
> To: cygwin@cygwin.com
> Subject: Cygwin: Interoperability Is Important (was Cygwin: Open or
> Closed System, etc)
> 
> 
>     ooh, very spicy.  i suppose i deserve it (full posting 
> attached below).
>     however i am also interested in improving the cygwin project and 
> making things better for the world.
>     i think you might have missed that part of the conversation 
> (referenced in your posting) had drifted away from zip in specific to 
> cygwin path handling in general.  i believe that the examples 
> i provided 
> for 'ls' demonstrate that this issue is not limited to the zip port. 
>  and as far as what i can see from reading the manual (user guide), 
> handling ms dos pathnames is a design goal for cygwin.

I'm not agreeing or disagreeing about the design goal. I simply want to
make a very small but important point... "cygwin" that is the
cygwin1.dll has full support for ms dos or more accurately win32
pathnames. Call fstat(), or fopen() or ... and give it a ms dos
pathname. If there is a real file with that msdos pathname the call will
behave as you would expect it to. 

Finito. Done. No problems. Possibly minor tweaks needed for performance
or bugfixing.

<snip>

> current directory on drive a.  i can't claim that with certainty now, 
> considering your mention of NTFS streams.  i've not encountered that 
> usage you're describing yet.  is that accessible in command prompts?

$ echo "c" > "foo"
$ echo "a" >  "foo:1" 
$ echo "b" > "foo:2"
 
now cat foo - it will still be "c". cat foo:1 and get "a".

Snip.

Rob

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/