On Dec 11 23:06, Roland Mainz via Cygwin wrote: > Hi! > > ---- > > I got a couple of bugreports that Cygwin $ getconf CASE_INSENSITIVE > /path # does not work and always reports that the filesystem is > case-insensitive - which is not true for NFSv3, and usually not true > for NFSv4.1 filesystems coming from Linux (NFSv4 supports > case-insensitive filesystems, but that is not the issue...) > > Example (/cygdrive/l/ is a case-sensitive filesystem): > ---- snip ---- > $ getconf CASE_INSENSITIVE /cygdrive/l/builds > 1 > $ getconf -a /cygdrive/l/builds | fgrep -i case > CASE_INSENSITIVE 1
Yes. Case sensitivity is a problem. It doesn't matter if the filesystem supports case sensitivity, if the OS or the mount mode doesn't support case sensitivity. The above flag is a result of checking all available information on the matter. THis may be helpful to understand the problem: https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive Corinna -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
