Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 19 Aug 2005 16:58:47 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Christopher Benson-Manica <ataru AT sdf DOT lonestar DOT org>
cc: cygwin AT cygwin DOT com
Subject: Re: Permissions, again
In-Reply-To: <20050819202459.GA23900@SDF.LONESTAR.ORG>
Message-ID: <Pine.GSO.4.61.0508191653180.16057@slinky.cs.nyu.edu>
References: <20050819194352 DOT GA28538 AT SDF DOT LONESTAR DOT ORG>  <Pine DOT GSO DOT 4 DOT 61 DOT 0508191608070 DOT 16057 AT slinky DOT cs DOT nyu DOT edu>  <20050819202459 DOT GA23900 AT SDF DOT LONESTAR DOT ORG>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 19 Aug 2005, Christopher Benson-Manica wrote:

> > chmod, and other POSIX programs know nothing about ACLs (which is where
> > inheritance is specified).  You should, however, be able to use
> > "getfacl/setfacl" to do what you want.
>
> Hm...  It seems that (get|set)facl do allow detailed permissions to be
> set, but what I really need is the inherited property/attribute/whatever
> to be set, as these files need to have permissions matching those of
> their final destinations.

I thought that was what the various "mask" ACLs did, but someone more
familiar with ACLs and getfacl/setfacl needs to chime in here...

> It's okay to tell me "Don't be absurd!" but I haven't heard it yet :-)

You can also try "cacls" and whatever the equivalent ACL modification tool
is from Microsoft.

> Incidentally, while I was using the ntsec default for permissions,
> all this stuff worked correctly...

You mean "nontsec", don't you?  In "nontsec" mode, Cygwin lets Windows
handle the file ACLs, which results in inherited permissions.

> Also, with umask set to 077, a file I create with "touch" will end up
> with NT permissions for read and write, but not execute, as well as
> numerous other types of permissions.

I believe POSIX mandates that "touch" use permissions 0666&~umask for new
files (i.e., the execute bits in the umask are ignored).
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/