From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4179 invoked by alias); 24 Oct 2014 09:55:47 -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 4168 invoked by uid 89); 24 Oct 2014 09:55:46 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: calimero.vinschen.de Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 24 Oct 2014 09:55:44 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 1FA1E8E1434; Fri, 24 Oct 2014 11:55:41 +0200 (CEST) Date: Fri, 24 Oct 2014 09:55:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Problems on case-sensitive file systems Message-ID: <20141024095541.GG20607@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <54475648.3000805@towo.net> <20141022140031.GD18857@calimero.vinschen.de> <5448F79A.6010900@towo.net> <20141023153609.GA20607@calimero.vinschen.de> <5449390F.5000903@towo.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YH9Qf6Fh2G5kB/85" Content-Disposition: inline In-Reply-To: <5449390F.5000903@towo.net> User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2014-10/txt/msg00388.txt.bz2 --YH9Qf6Fh2G5kB/85 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 3304 On Oct 23 19:21, Thomas Wolff wrote: > Am 23.10.2014 17:36, schrieb Corinna Vinschen: > >On Oct 23 14:42, Thomas Wolff wrote: > >>Am 22.10.2014 16:00, schrieb Corinna Vinschen: > >>>On Oct 22 09:01, Thomas Wolff wrote: > >>>>I'm facing a number of issues with case-sensitivity which I've collec= ted: > >>>> > >>>>There is a documented limitation on case-sensitivity using drive lett= er > >>>>paths, > >>>>also mentioned in https://sourceware.org/ml/cygwin/2013-08/msg00090.h= tml > >>>>(last item). I vaguely remember seeing a reason for this limitation i= n 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. > >>>The user expectation when using DOS paths is caseinsensitivity in the > >>>first place. But, as usual, there's no way to do this right, since > >>>somebody will have another POV. My stance is, don't use DOS paths when > >>>using Cygwin. At leats don't use DOS paths if you have any expectatio= ns > >>>about special POSIX path handling on Cygwin. > >>I use an application that uses Windows or mixed paths, I cannot influen= ce > >>it. So while I understand your POV, it would still be helpful to have p= ath > >>interpretation fully-featured. (If you point me to a place in winsup, I > >>might even try to do something myself.) > >I'm not going to apply a patch to do that. DOS paths get no special > >treatment, they are always handled with DOS/Windows defaults. > Any last chance to get a distinction here between X:\dos\paths and > X:/mixed/paths? As Andrey already wrote, it's pretty much the same thing. As soon as=20 you're using DOS paths (and drive letter paths with slashes are still DOS paths), the assumption is that the application expects DOS semantics. > >>I have now this in /etc/fstab: > >>C: /mnt/c ntfs binary,nouser,posix=3D1,noumount 0 0 > >>T: /mnt/t smbfs binary,user,posix=3D1,noumount,auto 0 0 > >Drop the noumount and it will work. noumount is an unknown mount flag > >and, FWIW, not documented in > >https://cygwin.com/cygwin-ug-net/using.html#mount-table > Ah! Thanks. > That reminds me of that other problem I had previously observed but > forgotten: > mount does not report option errors... Right. Mount doesn't know the valid options by itself. It gets a list by calling into the Cygwin DLL. The fact that mount doesn't check them and report unknown options is a bit awkward. Patches welcome. > Also: > mount suggests this problem itself by reporting that very unknown option > when running just 'mount' Uh, yes. This is the option historically printed for cygdrive mount points. It's not a valid option for fstab, though. > And as a last, minor issue: > mount does not work on relative paths (like it does on Unix/Linux) but ne= eds > an absolute path: > mount /mnt/c # works > cd /mnt; mount c # does not work This is historical, too. There never has gone much work into mount since it was most of the time "good enough". If you want to get relative pathname support for the POSIX side of mount points, feel free to hack away. It's a neat feature. Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --YH9Qf6Fh2G5kB/85 Content-Type: application/pgp-signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUSiIcAAoJEPU2Bp2uRE+g6LcP/jDlLshAqxqBKu06FK1QCQk2 duC/KQBj0FrPnkvoLZ/mGCR18EghY/J33/bLJ4ICGo+/PHqMvjyToXRJBqV7MdpK I/PTUt04I4a0Lnam7LgxpTHpfI4hT8COtkuBhYpbfYMAyyddri/hszi7DGRbdi8u A5DCjTCRXKxmLnM8LHLkPKC+Mdx75J4+NCwNtEh3s606QKMR6B9ODpkTJ9Dx1BN2 EXC0TQxkxMTag8RHW/tlWd08r5KKBjJb8ZnzIbRaQuAiz6yHI6Uf1VGmcAFA0Z2o OqLFi7OVwH4OwKN0asa8wFs+HtM6BEdtWUEeXZ/rRrWIJzKHtWCUv9yRd6BDvq2I /RJQRw7+jT0bucVGd+Xyk8LXOlOcifK+8jssbkUxTVFp3iiiD2EaV19mHB0mOTxL h3TAbtVWSbkYC6qwZE4vhfqzuNMIpjAb3alZFQdkoLHh9abfKOtp5GO50PzYWOLB URSAYEykyC2CRPHe8K7tiDGrAqR/l3z9baWNsnA3+W1x7VLgHl4yJmQvuy87jgwq o+dmTn0/yEMrcDR5T5g90P2Lfd7w/HXtynN9rSw7XQ09adNpldLXLQxtZvliTGdW A+vA/vM6BAF0qWGkYpiMHShHo0IWU7FG2bBJ3P0nYR1jfgKo/fo8PckNDt66ef4S pmOMneO7kpW9OlecG1j1 =Qezr -----END PGP SIGNATURE----- --YH9Qf6Fh2G5kB/85--