0
Many of the files in my home directory are executable for no good reason.
By 'executable' I mean that the -x flag is set (as shown by ls -al). When I write the file name, my shell completes the file name on tabbing.
This includes many PDF files, HTML files, and image files. I would never consider these to be executable. Trying to execute them produces error messages (I suppose) such as 'no job control'.
Why is the executable flag set, apparently be default, for so many files? I should mention that I am using Cygwin, but I have observed similar behavior on other machines (proper Linux) as well.
shuhalo
Posted 2017-08-02T18:55:07.917
Reputation: 175
1This is definitely not normal for "proper Linux" (which Cygwin isn't, because Windows permissions are entirely different). – slhck – 2017-08-02T19:11:04.930
which home directory, Windows one or cygwin home ? – matzeri – 2017-08-02T20:26:22.007
@matzeri: I have been looking at my home directory in Cygwin. – shuhalo – 2017-08-03T15:25:04.247
@slhck: It seems that most of the files in the windows file systems are considered executable by Cygwin. Even if they are created only via the shell. – shuhalo – 2017-08-03T15:29:35.370
check
umaskvalue. With normal0022the file created by cygwin programs should not be executable – matzeri – 2017-08-03T19:18:44.340