DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:content-type:content-transfer-encoding
	:subject:message-id:date:to:mime-version; q=dns; s=default; b=Vf
	9Jg4hLdAj/PyoD9XzBScjgF71Sw5o5B9Bu6M7TnOfnatQK9tFEiJeZ8xn/QIraS+
	P5EZihv3h5nVDXRYnNqt1aO8hwZILJH6PgfPL5zBjhBoaDoITDQRaxqnqNhp92vc
	TBKz5qF8kXxG2mDtdvGgSkKIzwqlQ8guX4a5AfPqM=
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
From: Duane Ellis <duane AT duaneellis DOT com>
Content-Type: text/plain; charset=utf-8
Subject: Re: File permissions different inside and outside cygwin root
Message-Id: <E087F37F-5AAF-4526-B6B8-091D8F9FDC20@duaneellis.com>
Date: Sun, 24 May 2015 08:02:32 -0700
To: cygwin AT cygwin DOT com
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Content-Transfer-Encoding: 8bit

(Sorry I cannot reply directly to the previous email I just subscribed to the list, I am quoting from the list archive)

>> (from the archive - permissions inside and outside of /cygwin get messed up)

I think this is *THE* cause of my problems.

My question is how do I turn this of 100% totally - and completely?

How it is effecting me:

In my case, I *OFTEN* edit source code using ‘emacs-w32’ under cygwin.

and often refer to files via  a filename like this /cygdrive/c/some/path/foo.c

Sadly what happens in the end is, the ACL gets set to the point where I cannot edit source files.

Another common example is this:

Step 1:  On Linux  - create a “tar.gz” of a source directory.

	tar cfz  foo.tar.gz  somedirectory

(In my case, it is an open source package that *must* build under both cygwin and linux)
I need to move the code back and forth - to make sure my changes don’t break things

Step 2:  Pull that tar file over to Cygwin (I use cygwin64)

Step 3: Unpack the tar.gz file using CYGWIN

	tar xfz foo.bar.tz

Step 4:	
	I specifically use “emacs-w32” - to edit the source code.
	It seems that *randomly* the ACL gets totally bunkered

	Maybe there is a method to this madness, but I can’t figure out the exact sequence

I am *NOT* building or doing this under  any Cygwin mount
I should not need to, and I should not be required to

I specifically use:  /cygdrive/c/some/path/

**NOTE**

   This does not *require* the ‘tar-copy’ method 
   Using CYGWIN - I “git clone” some repository and edit the files in the standard way
   It seems to be more predominant when I copy via TAR across systems.


Result:
	I can no longer edit my source code.
	I would end up having to “right click” permissions and fix things using windows tools

       It seems the ACLs are totally messed up

Bottom line, my expected behavior

	I should be able to use a simple editor - i.e.: Emacs-w32
	I should be able to edit a source code file
	When I save the source code file - the permissions *before* and *after* should be identical

	They are not, permissions are totally messed up.

	What ever I am seeing, it is fundamentally broken.

-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