X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org X-SpamScore: -5 X-BigFish: VPS-5(zz444fMzz1202hzzz2dh2a8h668h839h944h) X-Forefront-Antispam-Report: CIP:157.55.224.141;KIP:(null);UIP:(null);IPV:NLI;H:DB3PRD0502HT011.eurprd05.prod.outlook.com;RD:none;EFVD:NLI From: Tom Quarendon To: "cygwin AT cygwin DOT com" Subject: RE: File permissions problems with cp in Windows 7 Date: Thu, 16 Feb 2012 10:50:39 +0000 Message-ID: References: <4F3BF932 DOT 9080201 AT cygwin DOT com> In-Reply-To: <4F3BF932.9080201@cygwin.com> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 X-OriginatorOrg: teamwpc.co.uk X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id q1GApOUr019898 I am a member of the local administrators. It actually sounds like noacl is what we would want here. We are just using Cygwin shell as a basis for our build environment for ease of portability, but we're using Visual Studio etc, not building Cygwin executables. Not sure why I would actually want posix permissions for what we're doing. Noacl certainly fixed the problem, however it would be good to understand why it happens. In your attempt to reproduce, what does he getfacl show for the root /cygdrive/c directory? That seemed to be where the issue lay. Not sure whether what I see is to be expected. -- 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