Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Message-ID: <432F1978.DB503CF7@dessent.net>
Date: Mon, 19 Sep 2005 13:03:04 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Bug: Setup tool doesn't respect managed mountpoints/filesystems
References: <0IN2009A5RCXL6 AT pmismtp01 DOT mcilink DOT com>   <Pine DOT GSO DOT 4 DOT 63 DOT 0509191358260 DOT 21521 AT slinky DOT cs DOT nyu DOT edu> <432F06FB DOT 7A5422B6 AT dessent DOT net>  <Pine DOT GSO DOT 4 DOT 63 DOT 0509191502560 DOT 21521 AT slinky DOT cs DOT nyu DOT edu> <432F122A DOT ADF69285 AT dessent DOT net> <Pine DOT GSO DOT 4 DOT 63 DOT 0509191542200 DOT 21521 AT slinky DOT cs DOT nyu DOT edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Igor Pechtchanski wrote:

> Which was what I said in the part you snipped.

My skimming skills are not great today.  :(

> > Repeat for "readme" vs. "Readme" and every other of billions of
> > permutation of case.  I see no way this wouldn't turn into a nightmare.
> 
> Huh?  Why would you need to try *all* the permutations?

I guess I was conflating the fact that the *current* implementation
leaves lower-case and only encodes upper-case / special characters /
reserved words with the *proposed* implementation that would have to
either encode everything or encode nothing.

> Which may or may not be considerable (and no, I don't have measurements to
> back it up).  There is another overhead, and that is of a human trying to
> look at the directory with Windows tools.  Yes, encoding is unavoidable,
> but it shouldn't be obnoxious.

I know it's armchair quarterbacking but it seems to me like urlencoding
a filename (requiring no system calls, just string processing) would
have a lot less overhead than having to do double the number of calls to
CreateFile for nearly every file operation.

As far as the human-readable aspect goes, I consider managed mounts as
only being required in special or rare circumstances, and so I see
having uppercase letters fudged in Explorer is a price one can pay. 
Don't the majority of filenames consist of lowercase letters anyway? 
Those would remain untouched to native tools.

Brian

--
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/