drew
/
acadia-newlib
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

* effectively.sgml (using-shortcuts): Match chapter with reality.

This commit is contained in:
Corinna Vinschen 2010-03-12 10:33:08 +00:00
parent 3519b4c361
commit 36960dec37
2 changed files with 19 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
winsup/doc/ChangeLog
View File

@ -1,3 +1,7 @@
2010-03-12 Corinna Vinschen <corinna@vinschen.de>
* effectively.sgml (using-shortcuts): Match chapter with reality.
2010-03-11 Corinna Vinschen <corinna@vinschen.de> 2010-03-11 Corinna Vinschen <corinna@vinschen.de>
* faq-using.xml (faq.using.bloda): Add "Credant Guardian Shield". * faq-using.xml (faq.using.bloda): Add "Credant Guardian Shield".

29
winsup/doc/effectively.sgml
View File

@ -155,23 +155,24 @@ endings, but <systemitem>cygutils</systemitem> provides several dedicated progra
Another problem area is between Unix-style links, which link one file Another problem area is between Unix-style links, which link one file
to another, and Microsoft .lnk files, which provide a shortcut to a to another, and Microsoft .lnk files, which provide a shortcut to a
file. They seem similar at first glance but, in reality, are fairly file. They seem similar at first glance but, in reality, are fairly
different. By default, Cygwin uses a mechanism that creates symbolic different. By default, Cygwin does not create symlinks as .lnk files,
links that are compatible with standard Microsoft .lnk files. However, but there's an option to do that, see <xref linkend="using-cygwinenv"></xref>.
they do not include much of the information that is available in a These symlink .lnk files are compatible with Windows-created .lnk files,
standard Microsoft shortcut, such as the working directory, an icon, but they are still different. They do not include much of the information
etc. The <systemitem>cygutils</systemitem> package includes a that is available in a standard Microsoft shortcut, such as the working
<command>mkshortcut</command> directory, an icon, etc. The <systemitem>cygutils</systemitem>
utility for creating standard Microsoft .lnk files. package includes a <command>mkshortcut</command> utility for creating
standard native Microsoft .lnk files.
</para> </para>
<para> <para>
If Cygwin handled these native shortcuts like any other symlink, But here's the problem. If Cygwin handled these native shortcuts like any
you could not archive Microsoft .lnk files into <command>tar</command> other symlink, you could not archive Microsoft .lnk files into
archives and keep all the information in them. After unpacking, <command>tar</command> archives and keep all the information in them.
these shortcuts would have lost all the extra information and would After unpacking, these shortcuts would have lost all the extra information
be no different than standard Cygwin symlinks. Therefore these two types and would be no different than standard Cygwin symlinks. Therefore these two
of links are treated differently. Unfortunately, this means that the types of links are treated differently. Unfortunately, this means that the
usual Unix way of creating and using symlinks does not work with usual Unix way of creating and using symlinks does not work with native
Windows shortcuts. Windows shortcuts.
</para> </para>
</sect2> </sect2>