DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=CnGuV99VK7Zi/HP0X092DRyvKfhBoTTpC7qyZGYHgr2yXdH/erSqE
	RkqFNrHe8jbrAG4Qo74KpNJzZTL6Qzm8uH6H9qB31hgtUAMceXj/9Cct0i7K2C0Z
	kpKPc6vUQTQU6dk17mIOMm+6uglJINY3gdTlTDMTsy9e4rvONT5miM=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Thu, 23 Oct 2014 17:36:09 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Problems on case-sensitive file systems
Message-ID: <20141023153609.GA20607@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <54475648 DOT 3000805 AT towo DOT net> <20141022140031 DOT GD18857 AT calimero DOT vinschen DOT de> <5448F79A DOT 6010900 AT towo DOT net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="45Z9DzgjV8m4Oswq"
Content-Disposition: inline
In-Reply-To: <5448F79A.6010900@towo.net>
User-Agent: Mutt/1.5.23 (2014-03-12)

--45Z9DzgjV8m4Oswq
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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 collecte=
d:
> >>
> >>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.
> >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 expectations
> >about special POSIX path handling on Cygwin.
> I use an application that uses Windows or mixed paths, I cannot influence
> it. So while I understand your POV, it would still be helpful to have path
> 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.

> >>According to documentation, the posix mount flag is enforced to be the =
same
> >>for all mounts below /cygdrive; is there a strong reason?
> >Yes.  The flags are shared between all cygdrive paths.  If you need
> >something else, don;'t use the cygdrive path, but another, manually
> >added mount point.  Note that this:
> >
> >  none /cygdrive cygdrive binary,posix=3D0,user 0 0
> >  D: /cygdrive/d ntfs binary,nouser,posix=3D1,noumount 0 0
> >
> >does NOT work.  The manual paths must not overlap with the cygdrive
> >paths.
> I know and I did use a different path (maybe too similar to get
> recognized...). But it does not seem to work properly:
> 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


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--45Z9DzgjV8m4Oswq
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUSSBpAAoJEPU2Bp2uRE+gjx8P/1N1qmvyZDfYEKcaWXN1A5oJ
XdS2P/WXhidfpOPbkb3zgukUdDB8aXtkEMpOG/zfT/ZvFBCazmmXEFvzKCeEsZc8
zfItlomebnOuBJOKSG/LR9ks3YkxnJS0tK8OYjF6k5fOEUzORGXK/9B8q1ZmcKPY
mdR/kGziyXaWJil2Xjcmnki5Dc9Ou1m5PaQKmFZ3F48AsCLlZb3u06Q2OSapAefA
CIYH+hjf55If9DRh2XumhQTku5qqs5vrBYeh9H6bCpKVO1n45a/H8i9GtDX2V+yz
QJf4dyqH9Ubb20JEaKnzaooXUFex5IfP4MWMFPKJ1Z8qK+dvtee4rJN7t1+DgdWq
QlosyWxiZa8GndAW9ZCeL7kjoTtU2ml80R5tNnkNz2R00TJbvQ1fkO4/q59WNc8N
BSIpDjEcQG3AZIal4T1z69tKmLU3ZsHt+0VG6DmOACbksqZR9le+jvbv/XaxHMkJ
CMSddnBDq4KrIp7nAJ65x6IUAG5jTfnE0b+COeIprWLRj1ips+lHbyNoGZ7bGtrH
JVQvLR+AzSLbo8p5BAbn7mXYhfhHt6/4ISgjJc285R6GJsx3WmACjQpc2j3BftZD
N6zqba3DNV+P9hl2tpMgPrUNbhpTyScnfab9NET49rrVRKEDgDVyfR7UlHJLTOJK
+KWzGrke54jlbFe9GxiN
=ZI2e
-----END PGP SIGNATURE-----

--45Z9DzgjV8m4Oswq--