Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT 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: 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" To: "Fred T. Hamster" , 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 AT gruntose DOT com] > Sent: Wednesday, June 27, 2001 2:35 PM > To: cygwin AT cygwin DOT 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. > 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/