From: roger <roger@eskimo.com>
To: cygwin@cygwin.com
Subject: Cygwin's chmod +X
Date: Tue, 18 May 2004 20:02:00 -0000 [thread overview]
Message-ID: <1084910520.3901.35.camel@localhost3.localdomain> (raw)
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/
next reply other threads:[~2004-05-18 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 20:02 roger [this message]
2004-05-19 11:53 ` Chris January
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1084910520.3901.35.camel@localhost3.localdomain \
--to=roger@eskimo.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).