From: David Macek <david.macek.0@gmail.com>
To: cygwin@cygwin.com
Subject: Documentation on fstab out of date
Date: Sat, 18 Apr 2015 14:47:00 -0000 [thread overview]
Message-ID: <55326E6D.7010703@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
Hi. It seems to me that <https://cygwin.com/cygwin-ug-net/using.html#mount-table> is out of sync with actual Cygwin behaviour in few aspects. What's the established process on updating these docs? List of issues I found follows.
> Recognized options are binary, text, nouser, user, exec, notexec, cygexec, nosuid, posix=[0|1]. The meaning of the options is as follows.
There are more options, as can be seen below the cited paragraph.
> Files ending in certain extensions (.exe, .com, .bat, .btm, .cmd) are assumed to be executable.
My reading of fhandler_disk_file.cc suggests it's only .exe, .com, and .lnk these days.
Interestingly, nt_path_has_executable_suffix (only used in the rename syscall, AFAICT) looks for a different set of suffixes (.com, .dll, .exe, .scr, .sys).
> Files whose first two characters begin with '#!' are also considered to be executable.
According to has_exec_chars, the sniffing routine also looks for "MZ" (EXE/PE files) and ":\n" (batch files? (can anyone confirm this?)).
--
David Macek
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4234 bytes --]
next reply other threads:[~2015-04-18 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-18 14:47 David Macek [this message]
2015-04-18 17:21 ` Steven Penny
2015-04-18 18:55 ` David Macek
2015-04-20 9:22 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55326E6D.7010703@gmail.com \
--to=david.macek.0@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).