| delorie.com/archives/browse.cgi | search |
Christopher Faylor wrote: > > > I guess I have to look at the code. A file with a .exe extension is > supposed to be executable by default. It should even show up as -x. > That's without ntsec. With ntsec Cygwin reads the Windows ACL and attempts to translate it to Unix modes. The executability of a file (ultimately by Windows) shouldn't depend on ntsec, although the mode displayed by ls -l does. With ntsec you can chmod 666 a.exe and it won't be executable (even by clicking on it), although ls -l with nontsec will show x (that's an item I didn't understand in Jason't recent mail). > > Do you have an idea about why a fresh install on a new system would have > problems? Is this merely because there is no mkpasswd -d happening? That's the only reason I see, apart from multi-domain. Jason raised another issue: > My WAG is that /bin is 700 and owned by Administrators which causes > setup.exe to create .exe files with the same permissions. I have not followed setup, so ignore the questions if they are worn out: - Does setup attempt to control the modes of the files it unpack? - Do the modes depend on the value of ntsec when setup is run (e.g. inheriting from the directory)? Pierre
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |