From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12501 invoked by alias); 6 Apr 2011 00:35:55 -0000 Received: (qmail 12312 invoked by uid 22791); 6 Apr 2011 00:35:54 -0000 X-SWARE-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from radlog1.lnk.telstra.net (HELO midge.radlogic.com.au) (165.228.189.75) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 06 Apr 2011 00:35:44 +0000 Received: from groper.radnet.com.au (groper.radnet.com.au [10.1.1.1]) by midge.radlogic.com.au (8.13.1/8.13.1) with ESMTP id p360Zf1G015224 for ; Wed, 6 Apr 2011 10:05:41 +0930 Received: from gar (gar.radnet.com.au [10.1.1.77]) by groper.radnet.com.au (8.13.1/8.13.1) with ESMTP id p360ZbhT011889 for ; Wed, 6 Apr 2011 10:05:41 +0930 From: "Christian Gelinek" To: Subject: Re: NTFS write-protect flag translation (tar? rsync?) only one-way? Date: Wed, 06 Apr 2011 06:16:00 -0000 Message-ID: <000001cbf3f2$843bd520$8cb37f60$@com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-04/txt/msg00080.txt.bz2 -----Original Message----- From: Cygwin On Behalf Of Larry Hall (Cygwin) Sent: Wednesday, 6 April 2011 1:20 AM Subject: Re: NTFS write-protect flag translation (tar? rsync?) only one-way? > On 4/5/2011 3:36 AM, Christian Gelinek wrote: > > Hi everyone, > > > > I have a problem with the tar command with the "extract permissions > > information" option being set. > > > > I am running Cygwin (CYGWIN_NT-6.1-WOW64 1.7.8(0.236/5/3) 2011-03-01 09= :36) > > under Windows 7 (Windows 7 Professional N Ver 6.1 Build 7600) with NTFS= and > > the CYGWIN=3Dntsec environment variable. > > > > It appears that when tar reads files for adding to archives, it correct= ly > > interprets the Windows-set "R" attribute, which is also seen by ls under > > Cygwin. After extracting the files using tar though, only Cygwin's ls > > command seems to be aware of the read-only attribute; the attrib comman= d (as > > well as Explorer and other Windows-apps) see and handle the file as bei= ng > > writeable. >=20 > The read-only attribute is a "Windows" thing. Cygwin's utilities focus on > supporting POSIXy/Linuxy ways of doing things. You can't expect Cygwin's > tools to manage all of Window's permission facilities in the same way as > Windows does. The read-only flag is one case where you'll see a divergen= ce. > If you need that flag set, you'll need your own wrapper to set it based on > the POSIX (or ACL) permissions. The read-only attribute really is quite > anachronistic though IMO. It conflicts with the more powerful ACLs. If > you have the option, it's better not to use that flag. IMO the behaviour is inconsistent if the flag is used/interpreted on one (t= he read) operation but NOT being written/changed on the other (write) opera= tion. My approach would be either drop it completely or support it on both = ends (the preferred option). By the looks of it=20 (see http://sourceware.org/ml/cygwin/2002-05/msg00317.html), this problem h= as been addressed and potentially solved before, so I wonder if something i= s broken here. The background to all this is that I am using RCS (I know, almost as anachr= onistic as the read-only attribute, but that's dictated by my workplace) un= der both Windows and Linux and RCS relies heavily on the read-only attribut= e of files to be correct. IMO, it wouldn't hurt if the Cygwin tools would w= rite the Windows read-only attribute when they create a Cygwin read-only fi= le? Regards, Christian -- 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