Houder <houder <at> xs4all.nl> writes:
But I am missing some "Unix logic" here:
- I modified the permissions of the files (chmod u+x)
What makes you think that these files should be executable?
- invoked setup (using -B)
- rebaselst is content now, though
- it creates the same files '666' !!!!!
They don't need to be executable. It's all just text, and mode 666
means
read and writable to everyone. In fact they are later made read-only
since
they are written to just once on creation and then moved to .old on the
next
invocation.
- again, I invoke setup (using -B)
- now rebaselst complains ...
It complains about not being able to write to a file it creates with
writable permission. I can't see how that can happen nor how it's the
fault
of rebaselst if it does. It seems that maybe setup can't write the ACL
changes that go along with the chmod, which would indicate that it's
not
invoked as the same user that owns the directory (which, given the ACL
you've shown is the only one with that right).
As the files were created with the wrong permissions, I am not
surprised.
For the wrong reason, I suppose.
Regards,
Achim.
--
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