public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Linda Walsh <cygwin@tlinx.org>
To: Ilya Basin <basinilya@gmail.com>,
	"cygwin@cygwin.com" <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
Date: Mon, 26 Mar 2012 00:30:00 -0000	[thread overview]
Message-ID: <4F6FB87E.8050109@tlinx.org> (raw)
In-Reply-To: <304827643.20120325123534@gmail.com>

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]

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 -- nodosfilewarning lowers clutter --
especially when you have domain names. (and have references to paths with 
'domain\\user/xxyz' in them).


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

  reply	other threads:[~2012-03-26  0:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-25  8:35 Ilya Basin
2012-03-26  0:30 ` Linda Walsh [this message]
2012-03-26 10:21   ` Corinna Vinschen
2012-03-26 10:18 ` 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=4F6FB87E.8050109@tlinx.org \
    --to=cygwin@tlinx.org \
    --cc=basinilya@gmail.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).