This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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:
smime.p7s
Description: S/MIME Cryptographic Signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |