Symlink targets dereferenced when winsymlinks:native

David Macek david.macek.0@gmail.com
Tue Nov 24 19:51:00 GMT 2015


On 20. 11. 2015 10:29, Corinna Vinschen wrote:
> On Nov 19 19:53, David Macek wrote:
>> On 18. 11. 2015 20:48, Corinna Vinschen wrote:
>>> On Nov 18 19:13, David Macek wrote:
>>>> On 18. 11. 2015 18:55, Corinna Vinschen wrote:
>>>>> On Nov 17 23:28, David Macek wrote:
>>>>>> I went through the UG looking for differences between regular Cygwin
>>>>>> symlinks and NTFS symlinks, but couldn't find this documented. It
>>>>>> seems that when using winsymlinks:native, the target path is first
>>>>>> dereferenced before storing it in the link.
>>>>>
>>>>> It's a result of the native symlink being a Windows path.  The
>>>>> ultimate conversion from POSIX to Windows path dereferences all
>>>>> symlinks.
>>
>> Hmm. I just performed a test on my Cygwin installation and it doesn't
>> seem to match the described behavior.
> 
> Symlinks within the path, e.g : /home/foo/symlink/bar/baz
> 
> If the above symlink is not a native symlink, the above path
> converted to Windows notation
> 
>   C:\cygwin64\home\foo\symlink\bar\baz
> 
> is invalid.

Ah. Now I understand. Thanks.

-- 
David Macek

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4254 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://cygwin.com/pipermail/cygwin/attachments/20151124/d7552145/attachment.p7s>


More information about the Cygwin mailing list