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=bFhdNvnz0IcQKDXGr6YXo6bpxMbqxQGHlIkU9PqE6KxsFEkKYUcYx
	c2fpYbHALdtJZwx1o4q4CrhzLsdar3T0XgfEcN3ZLEjEEvk/Uy0zKiO5JiaD6YiU
	BrX3w6xHMfbdTQ9jJG0P8X/BbeVxlxdyloz3N7TPSi5mvUhWvxFbl0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Wed, 22 Oct 2014 16:00:31 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Problems on case-sensitive file systems
Message-ID: <20141022140031.GD18857@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <54475648.3000805@towo.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="x4pBfXISqBoDm8sr"
Content-Disposition: inline
In-Reply-To: <54475648.3000805@towo.net>
User-Agent: Mutt/1.5.23 (2014-03-12)

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

On Oct 22 09:01, Thomas Wolff wrote:
> I'm facing a number of issues with case-sensitivity which I've collected:
>=20
> 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 so=
me
> 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.

> According to documentation, the posix mount flag is enforced to be the sa=
me
> 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.  Use somehthing else instead:

 D: /drive_d ntfs binary,nouser,posix=3D1,noumount 0 0


Corinna

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

--x4pBfXISqBoDm8sr
Content-Type: application/pgp-signature

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

iQIcBAEBAgAGBQJUR7h/AAoJEPU2Bp2uRE+gwBkP/jDGKpBvUDDcpX6q+uMmlBiU
UGxZenG67b60lGCuXVAC0h8RDyX51Nm9HrlPSHi5aJw7V46/SEGW/BbNDCsWZH5F
wuaDFchRTlHX4G7wcwWWcN3o2uiTAYGBjLULIM4mU/4ZxYh3TwitBwMzAPbsloni
6kKfsx7PG47tJUL6WkUBrHy7zHrHEa9auKTdUusksyd67WZ3PbBXFRR+xjqmqwi9
RE0Exdv2oA1aneApoykZbJK6ojMoIhqpnccscAygQnHZ8kitgvqyRzS+GDGl8Kqq
Nf5JmdpUQxS6FokwaAmaAMDViRhg+DetRJ867MZikqdXNRtasY12vyldu2ouXG8f
WR/u/9DSOGGxLty9Ia5iZVsIhWD29O/E1N7gGTtj0U+vIYR2qRtnwKGb1CK1rcTf
XONutWeoUInNK+tFBE8Ur3yjR5gsvC/kBC5ymuWeyvAwPGYrVSZw7k/thSjbZnvQ
ygf1Tg7kXwWz4/pRrR1Rq6AFGDcqu9bCcLgdGP3ccBQ1FRZa8KkgVh0Pi/vI2BSe
wKUtb4Est2a3lfzZcebcjhCGVjIzANTxjRIg2aTlwa0iVBKF5xmf7D83Z9a8XmQ4
PKeKIJoR51P56zfnCKcjs+UxAI+DV4Tw3FUmJcSdy2pK5xm5awdQPEyFYJS40rty
iEV8QyHk/LkweouWGMUf
=2/zw
-----END PGP SIGNATURE-----

--x4pBfXISqBoDm8sr--