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

* cygwinenv.sgml: Explain transparent_exe option.

This commit is contained in:
Corinna Vinschen 2006-02-05 18:19:16 +00:00
parent fbae2bf864
commit 6fc6eeae96
2 changed files with 17 additions and 0 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 @@
2006-02-05 Corinna Vinschen <corinna@vinschen.de>
* cygwinenv.sgml: Explain transparent_exe option.
2006-02-01 Joshua Daniel Franklin <joshuadfranklin@yahoo.com>
* faq-setup.xml (faq.setup.what-packages):

13
winsup/doc/cygwinenv.sgml
View File

@ -167,6 +167,19 @@ order not to strip, specify <literal>title</literal> or <literal>title
nostrip_title</literal>.</para>
</listitem>
<listitem>
<para><envar>(no)transparent_exe</envar> - EXPERIMENTAL. Only use this
option if you're confident to be able to live with the consequences. If
set, several additional functions in Cygwin will handle files with .exe
suffix transparently. These functions are <function>link(2)</function>,
<function>open(2)</function>, <function>rename(2)</function>,
<function>symlink(2)</function>, <function>unlink(2)</function>,
<function>pathconf(3)</function>. So far, these functions have been
treated as too dangerous to act on files with .exe suffix if the .exe
suffix wasn't given explicitely in the file name argument, and this is
still the case if the transparent_exe option is not set. Default is not
set.
</listitem>
<listitem>
<para><envar>(no)traverse</envar> - This option only affects NT systems.
If set, Cygwin handles file permissions so that the parent directories'
permissions are checked, as it's default on POSIX systems. If not set,