Mail Archives: cygwin-developers/2003/03/06/15:48:42
On Thu, Mar 06, 2003 at 03:48:13PM -0500, Pierre A. Humblet wrote:
>Christopher Faylor wrote:
>>
>> On Thu, Mar 06, 2003 at 01:20:45PM -0500, Pierre A. Humblet wrote:
>> >Jason's problem is specific to a very peculiar setup and the only
>> >visible effects seem to be extra log entries.
>> >
>> >I would not delay 1.3.21 just waiting for this to be resolved.
>>
>> Ok. Thanks for the clarification. Much appreciated.
>
>YAW.
>
>Here is another clarification
>>> cd /
>>> chmod -R a+r .
>>> chmod -R a+x bin sbin usr/sbin usr/local/bin lib/gcc-lib
>>>
>
>>This is supposed to be fixed in 1.3.21, so we can hold off on the FAQ.
>
>1.3.21 will fix some of those but in lots of cases stat will still show
>that files installed by setup are not accessible.
Oh, right.
>Fixing the bulk of those awaits the soon/future/eventual setup.exe with
>ntsec patch.
>Even then I fear there will be remaining cases (wait and see).
>So a FAQ entry would not hurt.
Ok. David, are you listening? The very least the above should do no
harm -- other than to make some header files executable. I guess it
really should be:
chmod -R a+x bin sbin usr/sbin usr/local/bin lib/gcc-lib/*.exe
cgf
>I was also thinking that cygcheck could "getfacl /bin".
- Raw text -