From 36960dec3721fccc8eb931787a2656cf715bfc39 Mon Sep 17 00:00:00 2001 From: Corinna Vinschen Date: Fri, 12 Mar 2010 10:33:08 +0000 Subject: [PATCH] * effectively.sgml (using-shortcuts): Match chapter with reality. --- winsup/doc/ChangeLog | 4 ++++ winsup/doc/effectively.sgml | 29 +++++++++++++++-------------- 2 files changed, 19 insertions(+), 14 deletions(-) diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog index 03c6adfd1..0b029ef00 100644 --- a/winsup/doc/ChangeLog +++ b/winsup/doc/ChangeLog @@ -1,3 +1,7 @@ +2010-03-12 Corinna Vinschen + + * effectively.sgml (using-shortcuts): Match chapter with reality. + 2010-03-11 Corinna Vinschen * faq-using.xml (faq.using.bloda): Add "Credant Guardian Shield". diff --git a/winsup/doc/effectively.sgml b/winsup/doc/effectively.sgml index b1e38c35c..945414b6a 100644 --- a/winsup/doc/effectively.sgml +++ b/winsup/doc/effectively.sgml @@ -155,23 +155,24 @@ endings, but cygutils provides several dedicated progra Another problem area is between Unix-style links, which link one file to another, and Microsoft .lnk files, which provide a shortcut to a file. They seem similar at first glance but, in reality, are fairly -different. By default, Cygwin uses a mechanism that creates symbolic -links that are compatible with standard Microsoft .lnk files. However, -they do not include much of the information that is available in a -standard Microsoft shortcut, such as the working directory, an icon, -etc. The cygutils package includes a -mkshortcut -utility for creating standard Microsoft .lnk files. +different. By default, Cygwin does not create symlinks as .lnk files, +but there's an option to do that, see . +These symlink .lnk files are compatible with Windows-created .lnk files, +but they are still different. They do not include much of the information +that is available in a standard Microsoft shortcut, such as the working +directory, an icon, etc. The cygutils +package includes a mkshortcut utility for creating +standard native Microsoft .lnk files. -If Cygwin handled these native shortcuts like any other symlink, -you could not archive Microsoft .lnk files into tar -archives and keep all the information in them. After unpacking, -these shortcuts would have lost all the extra information and would -be no different than standard Cygwin symlinks. Therefore these two types -of links are treated differently. Unfortunately, this means that the -usual Unix way of creating and using symlinks does not work with +But here's the problem. If Cygwin handled these native shortcuts like any +other symlink, you could not archive Microsoft .lnk files into +tar archives and keep all the information in them. +After unpacking, these shortcuts would have lost all the extra information +and would be no different than standard Cygwin symlinks. Therefore these two +types of links are treated differently. Unfortunately, this means that the +usual Unix way of creating and using symlinks does not work with native Windows shortcuts.