public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: File permissions different inside and outside cygwin root
Date: Tue, 02 Jun 2015 07:00:00 -0000	[thread overview]
Message-ID: <1433228431.8324.22.camel@cygwin.com> (raw)
In-Reply-To: <CAAXzdLWk_NV_HB8ctbmaWdr_9z=NwGwu4GLeYox878z4Emwx+A@mail.gmail.com>

On Mon, 2015-06-01 at 19:01 -0500, Steven Penny wrote:
> On Mon, Jun 1, 2015 at 1:38 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote:
> > - Right click and select "Properties".
> > - Go to the "Security" tab.
> > - "Advanced".
> 
> For goodness sake, do not do this. Do not break your computer because Cygwin
> sucks at permissions. Just read my post on noacl and live with the compromise
> until they fix it:
> 
> http://cygwin.com/ml/cygwin/2015-05/msg00297.html
> 
> Do NOT listen to Barry, you can break your computer following his advice:

While you are welcome to disagree with someone's opinion, you need to do
so without personal attacks.  Please be sure to be more considerate in
your future interactions.

--
Yaakov



--
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  7:00 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 [this message]
2015-06-02 12:58       ` Buchbinder, Barry (NIH/NIAID) [E]
2015-06-02 14:53         ` Duane Ellis
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=1433228431.8324.22.camel@cygwin.com \
    --to=yselkowitz@cygwin.com \
    --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).