Rob Walker wrote:
# make it read-only the windows way
attrib +R ${FILE}
Note that the +R attribute (and attributes in general) has nothing to do
with ACLs or security, it's a completely different concept. FAT for
instance supports R/H/S/A attributes but otherwise has a total lack of
any form
Brian Dessent wrote:
Rob Walker wrote:
# make it read-only the windows way
attrib +R ${FILE}
Note that the +R attribute (and attributes in general) has nothing to do
with ACLs or security, it's a completely different concept. FAT for
instance supports R/H/S/A attributes but
Brian Dessent wrote:
Rob Walker wrote:
The output of the examination above shows me that cp -a doesn't
preserve Full Control for the owner on the copied file. Is this the
expected behavior under ntsec? If I use CYGWIN=nontsec, Full Control is
preserved.
Well cp is a POSIX program
Rob Walker wrote:
[RGW] Hm, looks simple... Why isn't this part of cp -a ?
You have to understand the history of things. In the classic unix
world, a file has an owner, a group, a mode, and several timestamps.
From the standpoint of what cp -a can manipulate portably, that's
basically it.
Thanks for your patience, Brian.
-Rob
Brian Dessent wrote:
Rob Walker wrote:
[RGW] Hm, looks simple... Why isn't this part of cp -a ?
You have to understand the history of things. In the classic unix
world, a file has an owner, a group, a mode, and several timestamps.
From the
5 matches
Mail list logo
