DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=F1BTflTa+6VnC5Mh
	EuX9+hvZbCqvE89wI8dMi8G5JgJh6trLn0iPfeu8orLU270D2OwlxIFhUL9uNCCj
	o3FkRy+cnichsoGY7byg+GJ/Df0PXxra2WGa5+My6ENqQsq+vgxAAAZWsCYR68iv
	nKI48CJa0JANUJdP3UnCf7CW/78=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-id: <537238F0.8070505@cygwin.com>
Date: Tue, 13 May 2014 11:23:28 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: How do start a cygwin shell session from a script ?
References: <CAPbWNKGufbzvGCQd4u4e3nNp5OteAWM=C7=AgE1z-UVoN6XzjA AT mail DOT gmail DOT com> <CAPbWNKFJMBDbyXH9S86+95L_Ak06auOn7BKnoqD9z1n7Ggtufg AT mail DOT gmail DOT com>
In-reply-to: <CAPbWNKFJMBDbyXH9S86+95L_Ak06auOn7BKnoqD9z1n7Ggtufg@mail.gmail.com>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit

On 05/13/2014 07:25 AM, Timothy Madden wrote:
> It appears I found my missing shell session settings: the access
> rights on the current build and source directories.
>
> The manual build was always run within the user home directory in
> cygwin, and cygwin could see the proper access right on all the files
> used in the build.
>
> But outside the user home directory, cygwin no longer sees the proper
> permissions for directories and files, even though the user running
> the cygwin session can very well read and write the files. But cygwin
> will list the files with no permissions whatsoever, not even u+r (read
> access for the file owner). If I use the Windows `icacls` command to
> explicitly add the current user to the ACL on the directory with
> inheritable (recursive) "full control" access right, than cygwin can
> see the proper access rights too for such directories.
>
> Can this issue maybe be fixed, so cygwin sees the same permissions, on
> any files, user that Windows will grant to the current user ?

There are some tools that only look at the POSIX permissions (rwxrwxrwx),
which is what Cygwin works to provide.  But if you're using non-Cygwin
tools to create or modify files, these will not necessarily comply with
POSIX permissions.  If using Cygwin alternatives for these tools isn't
an option, you can mount the directory tree in question with the "noacl"
option to tell Cygwin tools to always allow access (see
<http://cygwin.com/cygwin-ug-net/using.html#mount-table>).  Many
times, this approach works best when you're trying to mix Windows native
and Cygwin tools.


-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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