public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Duane Ellis <duane@duaneellis.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
Subject: Re: File permissions different inside and outside cygwin root
Date: Tue, 02 Jun 2015 14:53:00 -0000	[thread overview]
Message-ID: <17C46031-D529-4E0E-8086-09DE1B487F8F@duaneellis.com> (raw)
In-Reply-To: <6CF2FC1279D0844C9357664DC5A08BA2109F128B@msgb09.nih.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

  reply	other threads:[~2015-06-02 14:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-24 16:30 Duane Ellis
2015-06-01 18:44 ` Buchbinder, Barry (NIH/NIAID) [E]
2015-06-02  0:01   ` Steven Penny
2015-06-02  7:00     ` Yaakov Selkowitz
2015-06-02 12:58       ` Buchbinder, Barry (NIH/NIAID) [E]
2015-06-02 14:53         ` Duane Ellis [this message]
2015-06-05  3:53           ` Larry Hall (Cygwin)
  -- strict thread matches above, loose matches on Subject: below --
2015-05-21 13:05 DeTracey, Brendan
2015-05-22  1:32 ` Steven Penny

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17C46031-D529-4E0E-8086-09DE1B487F8F@duaneellis.com \
    --to=duane@duaneellis.com \
    --cc=BBuchbinder@niaid.nih.gov \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).