This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: 2.2.1: NTFS directory symlinks handling
- From: cyg Simple <cygsimple at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 24 Aug 2015 09:55:46 -0400
- Subject: Re: 2.2.1: NTFS directory symlinks handling
- Authentication-results: sourceware.org; auth=none
- References: <55D7C3E0 dot 3020703 at aosc dot xyz>
On 8/21/2015 8:35 PM, Mingye Wang (Arthur2e5) wrote:
> It is known that cygwin has a naive interpretation for NTFS symlinks, by
> translating those paths directly. This works fine with most cases, but
> when you link stuffs under `/` to somewhere like `../cygwin/home`, it
> simply breaks.
>
> I have a directory tree like this:
>
> |- cygwin/
> |- home/
> |- Arthur/
> |- .gnupg/ (mklink /D .gnupg \Users\Arthur\Appdata\Roaming\gnupg)
> |- .ssh/ (mklink /D .ssh \Users\Arthur\.ssh)
> |- tmp/
> |- 1.txt
> |- cygwin64/
> |- tmp@ (mklink /D tmp ..\cygwin\tmp)
> |- home@ (mklink /D home ..\cygwin\home)
>
> It appears that those `.gnupg` and `.ssh` with an absolute path to the
> drive root was interpreted correctly, like
> `/cygdrive/c/Users/Arthur/.ssh`, but cygwin64's /tmp and /home breaks,
> with the following manner described:
>
I would suggest to stick to absolute paths.
What happens when you "dir ..\cygwin"? I.E.: Is it a valid path to
begin with?
--
cyg Simple
--
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