Re: get git not to care about permissions
- From
- Matt Schoen <mtschoen@gmail.com>
- Date
- Nov 12, 2009, 15:47 UTC
- Message-ID
- <3cf217d80911120747k116d3747g75dc60f17e00127@mail.gmail.com>
- In-Reply-To
- <76c5b8580911120728j2f9995basb554b0a493a364bf@mail.gmail.com>
Thanks for the tip, Eugene, but I'm not sure if this helps me.
I'm trying to set up the repo on a shared directory, which isn't actually on a physical computer (NetApp is basically a data-server-in-a-box, and as such I do not directly interface with it). Thus, I must access the directory over the school network, which uses Kerberos security. I think it is this restriction that is giving git its issues.
On Thu, Nov 12, 2009 at 10:28 AM, Eugene Sajine <euguess@gmail.com> wrote:
Show 40 quoted lines
>>> >>> On Nov 9, 2009 11:06 AM, "sconeman" <schoen@bu.edu> wrote: >>> >>> >>> Hello, >>> >>> I'm trying to set up git on a NetApp drive at my school, BU. The NetApp >>> shares are configured with Windows permissions, and I forget the specifics >>> (which I can figure out if needed) about why this is the case, but basically >>> the deal is that if true UNIX permissions were to be used, Windows wouldn't >>> be able to read the drive. As such, and because we use the Kerberos >>> ticketing system, the permissions for the drive are set up such that the >>> owners (myself and my team members) have full permissions, but nobody else >>> does. Git doesn't like this and won't even create a bare repository. Is >>> there any way I can get git to ignore permissions and just do what it needs >>> to do? >>> >>> Thanks in advance for the help! >>> >>> -Matt >> -- > On Wed, Nov 11, 2009 at 4:34 PM, Eugene Sajine <euguess@gmail.com> wrote: >> Hi, >> >> I had almost similar issue - bare repos in my case should be set up under >> user which only few guys are having password from. So what I did is just a >> small program which creates the bare repo locally and makes secure copy to >> this user home. All authentication is hidden from the end user. Then users >> can access their repos via git protocol. Ialso fillthe repo with some >> additional info for cgit. >> >> Eugene > > BTW I'm using "git clone --bare" in this process, so if you have a > repo with working copy you can create a bare one separately, put it on > the server and then connect to it via "git remote add" > > Eugene > >