From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18029 invoked by alias); 5 Mar 2010 05:02:44 -0000 Received: (qmail 17956 invoked by uid 22791); 5 Mar 2010 05:02:42 -0000 X-SWARE-Spam-Status: No, hits=-3.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail16.tpgi.com.au (HELO mail16.tpgi.com.au) (203.12.160.231) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 05 Mar 2010 05:02:38 +0000 X-TPG-Abuse: host=[148.182.37.213]; ip=148.182.37.213; date=Fri, 5 Mar 2010 16:02:35 +1100; auth=+xHq3JwZYadZIHPPIIXj7mLD3QUfH+89GYY2HvrLPHs= Received: from [148.182.37.213] ([148.182.37.213]) (authenticated bits=0) by mail16.tpgi.com.au (envelope-from helium@shaddybaddah.name) (8.14.3/8.14.3) with ESMTP id o2552X95010015 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 5 Mar 2010 16:02:35 +1100 Message-ID: <4B909067.8050409@shaddybaddah.name> Date: Fri, 05 Mar 2010 05:02:00 -0000 From: Shaddy Baddah User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: cygwin-talk@cygwin.com Subject: Re: managed mounts. hindsight sadness at their departure References: <4B90817E.5020309@shaddybaddah.name> <4B9089A2.5070707@redhat.com> In-Reply-To: <4B9089A2.5070707@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-talk-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: cygwin-talk-owner@cygwin.com Reply-To: The Vulgar and Unprofessional Cygwin-Talk List Mail-Followup-To: cygwin-talk@cygwin.com X-SW-Source: 2010-q1/txt/msg00056.txt.bz2 Hi, On 5/03/2010 4:33 AM, Eric Blake wrote: > Request case sensitivity from windows, and you have that feature back. How embarrassing. I recalled fleetingly seeing something on case sensitivity in the 1.7 user manual, and checked back. But only the CYGWIN variable section. Seeing that it was restricted to globbing behaviour, I missed http://www.cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive >> Not that I'd assert that this is reason enough to have kept the managed >> mounts, it is just an unfortunate limitation that 1.7 now has over 1.5. > > No, it is not a limitation, provided you follow the instructions. > > $ touch a A > $ ls ? > A a Many thanks for pointing it out. I was completely unaware that Windows was capable of case sensitive file naming. I must admit that my entrenched views of Windows capabilities in this area make me a little bit apprehensive of possible side-effects to turning this on. In your experience, are there any? Of course, I will still try it anyway. Regards, Shaddy