Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Thu, 5 Jun 2003 15:13:07 -0400
From: Christopher Faylor <cgf-rcm AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Sparse file criteria malfunction - binutils produces sparse .exe & .dll files
Message-ID: <20030605191307.GA18497@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <006901c32b7f$0d7cceb0$78d96f83 AT pomello> <Pine DOT GSO DOT 4 DOT 44 DOT 0306051229390 DOT 25752-100000 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.44.0306051229390.25752-100000@slinky.cs.nyu.edu>
User-Agent: Mutt/1.4.1i

On Thu, Jun 05, 2003 at 12:41:18PM -0400, Igor Pechtchanski wrote:
>2) In all other details (including restricted characters in filenames),
>   Cygwin uses the underlying filesystem's conventions.  If we go out of
>   our way to be compatible with Linux in this aspect, why not also
>   support "aux" as the filename, or support '\' in filenames?  The
>   argument for not doing the latter was that we don't want to
>   disassociate ourselves from the underlying filesystem, IIRC, so why go
>   back on it now?

If there was a Windows call which allowed us to easily write, read,
rename, and delete special windows names, cygwin would use it.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/