Re: get git not to care about permissions
- From
- Matt Schoen <mtschoen@gmail.com>
- Date
- Nov 12, 2009, 21:44 UTC
- Message-ID
- <3cf217d80911121344w7d1809ebs103eaa2ac19a03a6@mail.gmail.com>
- In-Reply-To
- <200911121710.44314.trast@student.ethz.ch>
On Thu, Nov 12, 2009 at 11:10 AM, Thomas Rast <trast@student.ethz.ch> wrote:
Show 5 quoted lines
> It prints an absolute path, so the open() also accesses an absolute > path (though I don't know why it insists on that). > > But the above directory listing would indicate that you do not even > have permission to look inside your $(pwd) by absolute path...
I'm pretty sure I can. How can I test this? I can ls all subdirectories within the path, and when I navigate to the path, I usually do it absolutely. After all, this is a network share, so I have to start with "/ad/eng/...". Although, this is curious. Some of the directories show "d---------" when I do ls -al. They were created by root in the same environment (forced 700), but I can still read their contents, and such.
Does open() strictly require the permissions you give it? Like I mentioned, the permissions are locked at 700. Even if I try to chmod 777 the directory, I see no error, but the permissions remain unchanged. I'm thinking of doing a custom compile, removing those places where specific permissions are needed. My fear is that those places are many...