Fix inconsistencies in docs regarding fstab and executable file detection

The inline list of mount options seemed redundant, so the paragraph now points
to the list below it.

List of executable extensions updated according to fhandler_disk_file.cc. List
of executable magic numbers updated according to path.h (has_exec_chars).

	* pathnames.xml: Fix inconsistencies in docs regarding fstab and
	executable file detection

Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
This commit is contained in:
David Macek 2015-04-18 23:25:15 +02:00 committed by Corinna Vinschen
parent 5dc398f1d9
commit bbc87a02fd
1 changed files with 6 additions and 7 deletions

View File

@ -81,9 +81,8 @@ see <xref linkend="cygdrive"></xref></para>
<para>The fourth field describes the mount options associated <para>The fourth field describes the mount options associated
with the filesystem. It is formatted as a comma separated list of with the filesystem. It is formatted as a comma separated list of
options. It contains at least the type of mount (binary or text) plus options. It contains at least the type of mount (binary or text) plus
any additional options appropriate to the filesystem type. Recognized any additional options appropriate to the filesystem type. The list of
options are binary, text, nouser, user, exec, notexec, cygexec, nosuid, the options, including their meaning, follows.</para>
posix=[0|1]. The meaning of the options is as follows.</para>
<screen> <screen>
acl - Cygwin uses the filesystem's access control lists (ACLs) to acl - Cygwin uses the filesystem's access control lists (ACLs) to
@ -136,14 +135,14 @@ executability, this is not possible on filesystems which don't support
permissions at all (like FAT/FAT32), or if ACLs are ignored on filesystems permissions at all (like FAT/FAT32), or if ACLs are ignored on filesystems
supporting them (see the aforementioned <literal>acl</literal> mount option). supporting them (see the aforementioned <literal>acl</literal> mount option).
In these cases, the following heuristic is used to evaluate if a file is In these cases, the following heuristic is used to evaluate if a file is
executable: Files ending in certain extensions (.exe, .com, .bat, .btm, executable: Files ending in certain extensions (.exe, .com, .lnk) are
.cmd) are assumed to be executable. Files whose first two characters begin assumed to be executable. Files whose first two characters are "#!", "MZ",
with '#!' are also considered to be executable. or ":\n" are also considered to be executable.
The <literal>exec</literal> option is used to instruct Cygwin that the The <literal>exec</literal> option is used to instruct Cygwin that the
mounted file is "executable". If the <literal>exec</literal> option is used mounted file is "executable". If the <literal>exec</literal> option is used
with a directory then all files in the directory are executable. with a directory then all files in the directory are executable.
This option allows other files to be marked as executable and avoids the This option allows other files to be marked as executable and avoids the
overhead of opening each file to check for a '#!'. The overhead of opening each file to check for "magic" bytes. The
<literal>cygexec</literal> option is very similar to <literal>exec</literal>, <literal>cygexec</literal> option is very similar to <literal>exec</literal>,
but also prevents Cygwin from setting up commands and environment variables but also prevents Cygwin from setting up commands and environment variables
for a normal Windows program, adding another small performance gain. The for a normal Windows program, adding another small performance gain. The