From: Duane Ellis <duane@duaneellis.com>
To: Sky Diver <skydivergm@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: ACL Hell
Date: Thu, 16 Jul 2015 03:46:00 -0000 [thread overview]
Message-ID: <7FD22893-D2B2-4470-AF92-57C1F447DD6B@duaneellis.com> (raw)
In-Reply-To: <CADWQZEsakFsGe5g1wPMR-fqMYmkkk4cM62MweBFHwN0iaPLdHw@mail.gmail.com>
> I'm using cygwin for years already.
> I didn't use to have this problem in the past. It's something
> relatively new, that became way more intense in the past few months
> where I both re-installed windows at home, and got a fresh PC at work.
I had similar problems - and to fix them I did this:
Edit the file: /etc/fstab
Add “noacl” as an option for mount points - I just let all mount points be “windows default” and leave it.
It is in my opinion, the ACL stuff was well intended but ended up causing big problems for me.
Windows is just a very different beast, and does not implement POSIX very well, and no attempt at putting a square peg in a round hole ends well.
.
I think what Cygnus, then Redhat - etc has done is a marvelous and great good - but this ACL stuff - yuck.
I firmly believe “ACL = ON” by default is wrong headed.
-Duane.
--
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
prev parent reply other threads:[~2015-07-16 3:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 22:15 Sky Diver
2015-07-14 23:21 ` Steven Penny
2015-07-15 8:35 ` Andrey Repin
2015-07-15 14:52 ` Larry Hall (Cygwin)
2015-07-15 19:18 ` Sky Diver
2015-07-15 20:25 ` Sky Diver
2015-07-17 11:29 ` Kurt Franke
2015-07-23 15:29 ` Sky Diver
2015-07-16 3:46 ` Duane Ellis [this message]
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=7FD22893-D2B2-4470-AF92-57C1F447DD6B@duaneellis.com \
--to=duane@duaneellis.com \
--cc=cygwin@cygwin.com \
--cc=skydivergm@gmail.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).