From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3171 invoked by alias); 18 May 2004 20:02:29 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 3135 invoked from network); 18 May 2004 20:02:24 -0000 Received: from unknown (HELO mta9.adelphia.net) (68.168.78.199) by sourceware.org with SMTP; 18 May 2004 20:02:24 -0000 Received: from localhost4.localdomain ([68.169.121.157]) by mta9.adelphia.net (InterMail vM.5.01.06.08 201-253-122-130-108-20031117) with ESMTP id <20040518200223.ZSNY26615.mta9.adelphia.net@localhost4.localdomain> for ; Tue, 18 May 2004 16:02:23 -0400 Subject: Cygwin's chmod +X From: roger To: cygwin@cygwin.com Content-Type: text/plain Message-Id: <1084910520.3901.35.camel@localhost3.localdomain> Mime-Version: 1.0 Date: Tue, 18 May 2004 20:02:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2004-05/txt/msg00656.txt.bz2 I noticed while creating a bash script to backup my parents outlook & mydocuments folers, that WindowsXP does not recognize a "superuser" as being allowed access to a users folders! (bah. roger grumbles some more.) Anyways, I set out to mainly change these permissions myself within the script and yet found another bug while performing chmod a+X -R ./some_folder_with_subfolders (In brief, the -X set's the bit for folders to allow a user entry and -x is to set execution bit) I've found at times that issuing the "chmod a+X -R" would also give files execution permissions. I basically had to fiddle and found hack (or a way) around this issue by doing: cp -rf ./some_folder ./ chmod a+X -R ./some_folder I used the "cp -rf" option instead of "cp -ax" (or for preserving original permissions) and allowed the shell to specify permissions for new files. I would have loved to "cd /root_folder" ; "tar -cpvjf backup.tar.bz2 ./some_folder", however, I ran into problems with the reliability of using "chmod a+X" on the original file system (or paranoia of fiddling more with Windows -- ie "Why Fix something if it isn't -obviously- broke?") So basically, I'm copying the original folder to a tmp location and then removing them once tar is finished. This appears to be a MS Windows bug issue due to it's more relaxed file permissions? -- Roger http://www.eskimo.com/~roger/index.html -- 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/