On 02/03/2010 16:51, Charles D. Russell wrote:
> On 3/2/2010 3:15 AM, Larry Hall (Cygwin) wrote:
>>
>> Does <http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-ids>
>> answer your question?
>>
>
> Is there a short answer, one that does not require understanding how it
> all works? One thing I like about Cygwin is that I don't have to learn
> anything about Windows. So far I've always been able to get rid of
> intractable Windows files using Cygwin with chmod 777 and chown, but
> this seems to be an example where that won't work.
What, are you saying you also have a file called "foo.sh" that you can't
delete?! ;-)
Cygwin can't override the permissions enforced by the OS. It attempts to
/use/ those permissions to model the posix user/group/world model, but if a
file was created outside cygwin (i.e. in windows itself) there's no guarantee
the permissions set on it will make sense in the posix world. So... if you
actually really have the underlying OS permissions to change the access rights
to a file, chown/chmod will work; if you don't, they won't.
cheers,
DaveK
--
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
