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: <42719236.44C9FFBB@dessent.net>
Date: Thu, 28 Apr 2005 18:47:34 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: 1.5.16: Filename case sensitivity problem
References: <001201c54c59$b5926e00$fe01a8c0 AT dellpc>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Zhuang Jianmin wrote:

> 1. I can "tar jxvf setup-2.457.2.2.tar.bz2" to extract the setup package in the Cygwin environment, it works well, all files can be listed out. By under XP's file explorer, the filename with upper case is showed in a different form, for example, "%4Dakefile.am" but not "Makefile.am"

Please attach your cygcheck output as requested at
<http://cygwin.com/problems.html>.

It sounds like you have enabled managed mounts.  When you do that,
Cygwin encodes filenames with %nn.  This is so that filenames that are
normally forbidden by Windows (such as those that use reserved words
like CON, AUX, etc. or two files with the same name but different case)
can be used with Cygwin programs. Cygwin has to encode the filenames
specially to get around these inherent Windows limitataions.  They will
not show up correctly in Explorer because explorer has no idea what a
managed mount is.  When you extract the archive with winrar, the %nn
encodings will not be done, and since the directory is mounted in
managed mode, Cygwin will expect to see the encodings, which is why you
get file not found.

So, the solution is either:

- Don't use use managed mounts.
- Use managed mounts, but be aware that filenames will look strange to
non-Cygwin programs.

For most people there is absolutely no need to use managed mounts, and
it appears that you have enabled this feature without knowing how it
works or what it implies.  You should not be using this feature if you
don't understand it.  However, do not simply disable it now.  If you
have created files on a managed mount and then decide to mount those
paths normally, you will find lots of screwed up filenames.  To "undo" a
manged mount requires that you copy the entire tree to another path,
because you can't just turn off the managed mode once you've created
files there.

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/