From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6770 invoked by alias); 22 Oct 2014 07:01:37 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 6753 invoked by uid 89); 22 Oct 2014 07:01:36 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 X-HELO: mout.kundenserver.de Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (212.227.126.187) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 22 Oct 2014 07:01:34 +0000 Received: from [192.168.2.107] (dslb-088-073-011-163.088.073.pools.vodafone-ip.de [88.73.11.163]) by mrelayeu.kundenserver.de (node=mreue007) with ESMTP (Nemesis) id 0MG40o-1XsOel3ZiQ-00EuJ4; Wed, 22 Oct 2014 09:01:29 +0200 Message-ID: <54475648.3000805@towo.net> Date: Wed, 22 Oct 2014 07:01:00 -0000 From: Thomas Wolff User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Problems on case-sensitive file systems Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-UI-Out-Filterresults: notjunk:1; X-IsSubscribed: yes X-SW-Source: 2014-10/txt/msg00326.txt.bz2 I'm facing a number of issues with case-sensitivity which I've collected: There is a documented limitation on case-sensitivity using drive letter paths, also mentioned in https://sourceware.org/ml/cygwin/2013-08/msg00090.html (last item). I vaguely remember seeing a reason for this limitation in some mail but can't find it again. I think it would be good to remove this limitation because it breaks user expectations when working on case-sensitive drives. Note I'm not asking about EXFAT (as in that thread) but using Windows or mixed paths on NTFS or network drives, which should be easy to transform/normalize for access. According to documentation, the posix mount flag is enforced to be the same for all mounts below /cygdrive; is there a strong reason? I think this is not useful, because you may likely want data drives to be case-sensitive but it's not good for the Windows system drive (because Windows is so silly to have something like C:\WINDOWS\system32 in the path while the names are C:\Windows\System32... as a workaround, I once set a symbolic link into C:\ - ln -s WINDOWS Windows. This worked nicely until I wanted to reboot and it didn't find it's system folder anymore :( ). To achieve the desired mount, I tried this: D: /drives/d ntfs binary,nouser,posix=1,noumount but somehow it does not seem to work for local drives while it works nicely for network drives. mv XY xy does not work if XY is a directory (no effect, no message) If I switch Windows to case-sensitivity, there is no .EXE magic (only .exe magic). So e.g. PING: command not found, while PING.EXE works. Well, there are only a few .EXE files around, so this may be acceptable. ------ Thomas -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple