Date: Mon, 26 Mar 2012 12:21:11 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: du crashes if .lnk symlink and a folder it points to are named the same, differing only in letter case
Message-ID: <20120326102111.GM2425@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <304827643.20120325123534@gmail.com> <4F6FB87E.8050109@tlinx.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <4F6FB87E.8050109@tlinx.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Mar 25 17:29, Linda Walsh wrote:
> Ilya Basin wrote:
> 
> >I needed that because one git repository has branches named
> >"Epam/a" and "epam/b", and git was always creating the "missing" epam
> >directory at fetch.
> >
> >$ ls -l
> >total 0
> >drwxr-xr-x+ 1 adminpwd None 0 Mar 25 11:42 Epam
> >drwxr-xr-x+ 1 adminpwd None 0 Mar 25 11:42 epam
> >
> >why no " -> Epam" part? 'ls' behaves funny too, but at least it
> >doesn't crash.
> >
> >
> >$ ls -l epam.lnk
> >lrwxrwxrwx 1 Users None 4 Mar 13 16:43 epam.lnk -> Epam
> >
> >$ du .
> >0       ./Epam
> >Aborted (core dumped)
> 
> =====
> You might try setting going into system properties, advanced,
> Environment Variables and creating an entry (or adding to the
> original if there is one there already) for CYGWIN.  Entries to have
> in it:\
> winsymlinks export    #(+opt) [nodosfilewarning]

This problem has nothing to do with dosfilewarning.

> I have  a feeling you are seeing probs related to the cygwin hard link emulation
> which can by turned off by telling it to use winsymlinks (export
> tells it to export the value to children processes --

Sigh.  This problem has nothing to do with hardlinks.  And it has
nothing to do with the winsymlinks option, unless you count in the fact
that the symlink in question is a .lnk style symlink.  And the
winsymlink option has nothing to do with hardlinks at all.  There's a
reason the option is called winsymlink, not winhardlinks.


Corinna

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

--
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