On Sun, Feb 22, 2004 at 09:08:01PM +0100, Hannu E K Nevalainen wrote:
>A peculiar problem, this:
>
>I can reproduce it with 1.5.7-1 and the snapshot listed below. Others _not_
>verified.
>The workaround *seems* to be to enclose $CYGWIN contents in quotes (does
>this affect the requested functionality? <- untested )
Yes, sprinking quotes in the CYGWIN environment variable affects how it
interprets options. Cygwin doesn't know anything about quotes.
>$ uname -a
>CYGWIN_NT-5.0 P450 1.5.8s(0.110/4/2) 20040221 17:58:57 i686 unknown unknown
>Cygwin
>--
>
>$ cd /
>bash: cd: /: No such file or directory
>$ echo $CYGWIN
>notitle glob check_case:strict
^^^^^^^^^^^^^^^^^
Either turn this off or make sure that your root directory (e.g.
c:\cYgWiN) has the same case on disk as in your mount table (e.g.
c:\CyGwIn). Otherwise cygwin won't be able to find your root
directory.
I keep pointing out that there few reasons to use the check_case:strict
option. Even the person who wrote it (Corinna) agrees. It slows down
cygwin's file handling. You should only be using this option if you
really need it and really know what you are doing.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
