From: Andrey Repin <anrdaemon@yandex.ru>
To: Ulli Horlacher <framstag@rus.uni-stuttgart.de>, cygwin@cygwin.com
Subject: Re: umask problem: wrong permissions for new files
Date: Fri, 27 Apr 2018 09:05:00 -0000 [thread overview]
Message-ID: <1823587349.20180427115440@yandex.ru> (raw)
In-Reply-To: <20180426143827.GA27620@rus.uni-stuttgart.de>
Greetings, Ulli Horlacher!
> On Fri 2018-04-20 (07:25), Brian Inglis wrote:
>> Cygwin supports Windows ACLs as POSIX ACLs, which are also supported by
>> Linux. Use setfacl to set similar default ACLs (DACLs) on a Linux
>> directory, rerun your test there, and you should see similar results.
> (How) can I completly remove ACLs from the cygwin files and directories?
You CAN, yes.
However, you will lose any way to access the files, as explained below.
> The standard UNIX permissions are sufficent for my needs and much easier
> to handle :-}
"Standard POSIX" permissions are insufficient even for most basic operations.
They survive only because removing them would cause even more harm, than
letting them sit around.
>> *Never* remove DACLs from any Windows directory which will *ever* be used
>> with any non-Cygwin Windows program: /undefined behaviour/ will result.
> Uuups... thanks for the warning!
--
With best regards,
Andrey Repin
Friday, April 27, 2018 11:52:38
Sorry for my terrible english...
--
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
next prev parent reply other threads:[~2018-04-27 9:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 10:04 Ulli Horlacher
2018-04-20 12:47 ` Houder
2018-04-20 12:53 ` Houder
2018-04-20 13:07 ` Corinna Vinschen
2018-04-20 13:25 ` Brian Inglis
2018-04-26 14:38 ` Ulli Horlacher
2018-04-27 9:05 ` Andrey Repin [this message]
2018-04-27 9:27 ` Eliot Moss
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=1823587349.20180427115440@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=framstag@rus.uni-stuttgart.de \
/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).