From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: cygwin@cygwin.com
Subject: Re: umask problem: wrong permissions for new files
Date: Thu, 26 Apr 2018 14:38:00 -0000 [thread overview]
Message-ID: <20180426143827.GA27620@rus.uni-stuttgart.de> (raw)
In-Reply-To: <6cd38c2e-2271-aaee-3263-babf905325c1@SystematicSw.ab.ca>
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?
The standard UNIX permissions are sufficent for my needs and much easier
to handle :-}
> *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!
--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart E-Mail: horlacher@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de/
REF:<6cd38c2e-2271-aaee-3263-babf905325c1@SystematicSw.ab.ca>
--
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-26 14:38 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 [this message]
2018-04-27 9:05 ` Andrey Repin
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=20180426143827.GA27620@rus.uni-stuttgart.de \
--to=framstag@rus.uni-stuttgart.de \
--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).