From c33794d202fe76b156ec8753408eb95aa39cc417 Mon Sep 17 00:00:00 2001 From: David Macek Date: Tue, 24 Nov 2015 23:59:01 +0100 Subject: [PATCH] Add a section describing peculiarities of how Cygwin creates NTFS symlinks First take on how to describe dereferencing of Cygwin-only symlinks path components when creating NTFS symlinks. Note that I haven't tried building the documentation, so I don't know if the added paragraph breaks anything. Hopefully not. * pathnames.xml: Add a section describing peculiarities of how Cygwin creates NTFS symlinks. Signed-off-by: Corinna Vinschen --- winsup/doc/ChangeLog | 5 +++++ winsup/doc/pathnames.xml | 3 +++ 2 files changed, 8 insertions(+) diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog index 9185f21cb..ec9f40f7a 100644 --- a/winsup/doc/ChangeLog +++ b/winsup/doc/ChangeLog @@ -1,3 +1,8 @@ +2015-11-24 David Macek + + * pathnames.xml: Add a section describing peculiarities of how Cygwin + creates NTFS symlinks. + 2015-11-24 David Macek * faq-using.xml: Add Forefront TMG to the BLODA. diff --git a/winsup/doc/pathnames.xml b/winsup/doc/pathnames.xml index cdbf9fad6..9077303b4 100644 --- a/winsup/doc/pathnames.xml +++ b/winsup/doc/pathnames.xml @@ -407,6 +407,9 @@ these two settings, see . On AFS, native symlinks are the only supported type of symlink due to AFS lacking support for DOS attributes. This is independent from the winsymlinks setting. +Creation of native symlinks follows special rules to ensure the links +are usable outside of Cygwin. This includes dereferencing any Cygwin-only +symlinks that lie in the target path.