Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: ericblake AT comcast DOT net (Eric Blake)
To: Carlo Florendo <list-subscriber AT hq DOT astra DOT ph>, cygwin AT cygwin DOT com
Subject: Re: ln, ls or readline problem?
Date: Wed, 09 Nov 2005 01:25:13 +0000
Message-Id: <110920050125.19316.43714FF90005798E00004B7422007507840A050E040D0C079D0A@comcast.net>

> $ ls -ld bar2
> lrwxrwxrwx  1 Carlo None 7 Nov  9 08:47 bar2 -> foo/bar
> 
> Here's the problem:
> 
> When I  do a `cd bar2' and do an `ls -l ../', here's what I get:

Known problem.  Cygwin takes a shortcut and treats name/.. as
though it were a single ., which unfortunately is counter to posix
when name was a symlink.  The problem is that patching cygwin
is likely to slow down the common case, so the cygwin developers
have chosen speed over correctness for the moment on this issue.

--
Eric Blake



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