JehanneOS/newlib
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Add a section describing peculiarities of how Cygwin creates NTFS symlinks

Browse Source 
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 <corinna@vinschen.de>
This commit is contained in:
David Macek
2015-11-24 23:59:01 +01:00
committed by Corinna Vinschen
parent 76b5c03bd7
commit c33794d202
2 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
winsup/doc/ChangeLog
View File

@@ -1,3 +1,8 @@
2015-11-24 David Macek <david.macek.0@gmail.com>
* pathnames.xml: Add a section describing peculiarities of how Cygwin
creates NTFS symlinks.
2015-11-24 David Macek <david.macek.0@gmail.com> 2015-11-24 David Macek <david.macek.0@gmail.com>
* faq-using.xml: Add Forefront TMG to the BLODA. * faq-using.xml: Add Forefront TMG to the BLODA.

3
winsup/doc/pathnames.xml
View File

@@ -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 On AFS, native symlinks are the only supported type of symlink due to
AFS lacking support for DOS attributes. This is independent from the AFS lacking support for DOS attributes. This is independent from the
<literal>winsymlinks</literal> setting.</para> <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>
<listitem> <listitem>