From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Problems on case-sensitive file systems
Date: Thu, 23 Oct 2014 12:42:00 -0000 [thread overview]
Message-ID: <5448F79A.6010900@towo.net> (raw)
In-Reply-To: <20141022140031.GD18857@calimero.vinschen.de>
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 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.
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.)
>> 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.
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=1,noumount 0 0
T: /mnt/t smbfs binary,user,posix=1,noumount,auto 0 0
which has no effect at all. Neither are these mounts set automatically
when starting cygwin, nor can I refer to them by 'mount /mnt/t' ("mount:
can't find /mnt/t in /etc/fstab or in /etc/fstab.d/$USER") or 'mount -a'
(no effect).
The only thing that works is manual mounting:
mount -o posix=1 C: /mnt/c
mount -o posix=1,exec T: /mnt/t
But: while case-sensitivity now works in /mnt/c, it still does not in
/mnt/t.
As a minor side-effect, the mount points in /cygdrive of these two
drives now disappear from the list shown by 'mount' although they are
still available as duplicate mounts.
------
Thomas
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-10-23 12:42 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
2014-10-23 12:42 ` Thomas Wolff [this message]
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=5448F79A.6010900@towo.net \
--to=towo@towo.net \
--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).