This is the mail archive of the
mailing list for the Cygwin project.
Re: /bin/rebaselst: cannot create /var/cache/rebase/rebase_lst: Permission denied
- From: Achim Gratz <Stromeko at NexGo dot DE>
- To: cygwin at cygwin dot com
- Date: Fri, 8 Apr 2016 10:31:10 +0000 (UTC)
- Subject: Re: /bin/rebaselst: cannot create /var/cache/rebase/rebase_lst: Permission denied
- Authentication-results: sourceware.org; auth=none
- References: <065b7c7adc9b367aa54d7654d1e2550f at xs4all dot nl> <loom dot 20160408T110800-293 at post dot gmane dot org> <096364f9dabfcf3dcc897f9215839211 at xs4all dot nl>
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
> - 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
For the wrong reason, I suppose.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple