public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Problems on case-sensitive file systems
Date: Wed, 22 Oct 2014 14:00:00 -0000	[thread overview]
Message-ID: <20141022140031.GD18857@calimero.vinschen.de> (raw)
In-Reply-To: <54475648.3000805@towo.net>

[-- Attachment #1: Type: text/plain, Size: 1615 bytes --]

On Oct 22 09:01, Thomas Wolff wrote:
> 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.

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 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=0,user 0 0
 D: /cygdrive/d ntfs binary,nouser,posix=1,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=1,noumount 0 0


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2014-10-22 14:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22  7:01 Thomas Wolff
2014-10-22 13:52 ` Eric Blake
2014-10-22 13:55   ` Corinna Vinschen
2014-10-22 14:00 ` Corinna Vinschen [this message]
2014-10-23 12:42   ` Thomas Wolff
2014-10-23 15:36     ` Corinna Vinschen
2014-10-23 17:21       ` Thomas Wolff
2014-10-23 22:05         ` Andrey Repin
2014-10-24  9:55         ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141022140031.GD18857@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).