This is the mail archive of the cygwin-patches mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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 --- winsup/doc/pathnames.xml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/winsup/doc/pathnames.xml b/winsup/doc/pathnames.xml index cdbf9fa..9077303 100644 --- a/winsup/doc/pathnames.xml +++ b/winsup/doc/pathnames.xml @@ -407,6 +407,9 @@ these two settings, see <xref linkend="using-cygwinenv"></xref>. On AFS, native symlinks are the only supported type of symlink due to AFS lacking support for DOS attributes. This is independent from the <literal>winsymlinks</literal> setting.</para> +<para>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.</para> </listitem> <listitem> -- 2.6.2.windows.1 -- David Macek
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |