This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: File permissions different inside and outside cygwin root
- From: Duane Ellis <duane at duaneellis dot com>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Cc: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder at niaid dot nih dot gov>
- Date: Tue, 2 Jun 2015 07:53:15 -0700
- Subject: Re: File permissions different inside and outside cygwin root
- Authentication-results: sourceware.org; auth=none
- References: <E087F37F-5AAF-4526-B6B8-091D8F9FDC20 at duaneellis dot com> <6CF2FC1279D0844C9357664DC5A08BA2109EFF1F at msgb09 dot nih dot gov> <CAAXzdLWk_NV_HB8ctbmaWdr_9z=NwGwu4GLeYox878z4Emwx+A at mail dot gmail dot com> <1433228431 dot 8324 dot 22 dot camel at cygwin dot com> <6CF2FC1279D0844C9357664DC5A08BA2109F128B at msgb09 dot nih dot gov>
[paraphrased, and edited]
(Duane) describing the problem
(Barry) .. click click click right click .. click click to undo this crazyness
(steve) DO not do this .. you can break things in really bad ways
I would agree, I did not have time to reply yet.
My comment would be this:
This is not an appropriate solution - is very HUMAN ERROR prone
It does not scale well to others not familiar with the process.
Cygwin should just work, or the feature that causes this should be disabled
assuming that it is the ACLs, my questions are
1) How do I disable the ACL feature completely?
2) How can I determine if the ACL feature is enabled?
I need to put this test in a few build scripts
I need to prevent execution if the situation exists
if `SOMETEST`
then
echo âFIX THIS BUILD FAILâ
exit 1
fi
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple