On 07/24/2011 03:25 AM, Ryan Schmidt wrote:
On Jul 23, 2011, at 03:27, Andy Canfield wrote:
On 07/21/2011 07:27 PM, Cooke, Mark wrote:
I don't use *nix much but shouldn't that be `chown -R ...`?
Nope, the format of that command on Linux is
chown username.groupname fileselector
Generally c
On Jul 23, 2011, at 03:27, Andy Canfield wrote:
> On 07/21/2011 07:27 PM, Cooke, Mark wrote:
>> I don't use *nix much but shouldn't that be `chown -R ...`?
>
> Nope, the format of that command on Linux is
>chown username.groupname fileselector
> Generally chown has to be run as root in order t
On Sat, Jul 23, 2011 at 4:27 AM, Andy Canfield wrote:
> I would like to comment here that I've given up the idea of automatically
> giving repository access users with an existing login. While it's not a
> problem now, it is quite possible that in the future we'll have people with
> server logins
On 07/21/2011 07:27 PM, Cooke, Mark wrote:
-Original Message-
From: Andy Canfield [mailto:andy.canfi...@pimco.mobi]
Sent: 21 July 2011 13:19
To: nka...@gmail.com
Cc: users@subversion.apache.org
Subject: Re: Subversion: existing users
On 07/21/2011 05:55 PM, Andy Levy wrote
On 7/22/2011 1:45 AM, Andy Canfield wrote:
>
>> Welcome to sys-admin hell, the "documentation is true, but not
>> complete" world that I've spent so many years in. The connections
>> between different pieces of information that are obvious to someone
>> who's been through similar issues in the pas
On 07/21/2011 09:33 PM, Nico Kadel-Garcia wrote:
On Thu, Jul 21, 2011 at 6:12 AM, Andy Canfield wrote:
ADDENDUM ...
I used root to create the /data/svn directory. Then, anticpiating problems,
I did a chmod to make it writable to all.
Later I ran svnadmin create /data/svn/sample and it creat
On Thu, Jul 21, 2011 at 6:12 AM, Andy Canfield wrote:
> ADDENDUM ...
>
> I used root to create the /data/svn directory. Then, anticpiating problems,
> I did a chmod to make it writable to all.
>
> Later I ran svnadmin create /data/svn/sample and it created an entire
> repository directory tree und
> -Original Message-
> From: Andy Canfield [mailto:andy.canfi...@pimco.mobi]
> Sent: 21 July 2011 13:19
> To: nka...@gmail.com
> Cc: users@subversion.apache.org
> Subject: Re: Subversion: existing users
>
>
>
> On 07/21/2011 05:55 PM, Andy Levy wrote:
&
On Thu, Jul 21, 2011 at 08:18, Andy Canfield wrote:
>
>
> On 07/21/2011 05:55 PM, Andy Levy wrote:
>
> On Thu, Jul 21, 2011 at 06:12, Andy Canfield
> wrote:
>
> ADDENDUM ...
>
> I used root to create the /data/svn directory. Then, anticpiating problems,
> I did a chmod to make it writable to all.
On 07/21/2011 05:55 PM, Andy Levy wrote:
On Thu, Jul 21, 2011 at 06:12, Andy Canfield wrote:
ADDENDUM ...
I used root to create the /data/svn directory. Then, anticpiating problems,
I did a chmod to make it writable to all.
Giving global write permission will lead to problems as well.
Diffe
On Thu, Jul 21, 2011 at 00:36, Andy Canfield wrote:
>>> Alternatively, the SVN protocol will go to the svnserve program.
>>> Below the mod_dav_syn layer and the svnserve layer and the repository
>>> local
>>> layer is the "Subversion Repository". Significantly, this is diagrammed
>>> as
>>> data,
On Thu, Jul 21, 2011 at 06:12, Andy Canfield wrote:
> ADDENDUM ...
>
> I used root to create the /data/svn directory. Then, anticpiating problems,
> I did a chmod to make it writable to all.
Giving global write permission will lead to problems as well.
Different problems, but problems nonetheless
ADDENDUM ...
I used root to create the /data/svn directory. Then, anticpiating
problems, I did a chmod to make it writable to all.
Later I ran svnadmin create /data/svn/sample and it created an entire
repository directory tree under /data/svn. I don't remember but I
probably ran it as root.
Great...
On 07/21/2011 10:01 AM, Andy Levy wrote:
On Wed, Jul 20, 2011 at 22:42, Andy Canfield wrote:
Thank you very much.
On 07/20/2011 05:44 PM, Stefan Sperling wrote:
On Wed, Jul 20, 2011 at 05:22:57PM +0700, Andy Canfield wrote:
One quirk is that if he URL specifies direct access, e.t.
On Wed, Jul 20, 2011 at 22:42, Andy Canfield wrote:
> Thank you very much.
>
> On 07/20/2011 05:44 PM, Stefan Sperling wrote:
>
> On Wed, Jul 20, 2011 at 05:22:57PM +0700, Andy Canfield wrote:
>
> One quirk is that if he URL specifies direct access, e.t. svn ...
> file:///var/svn/RepoName, then wh
Thank you very much.
On 07/20/2011 05:44 PM, Stefan Sperling wrote:
On Wed, Jul 20, 2011 at 05:22:57PM +0700, Andy Canfield wrote:
One quirk is that if he URL specifies direct access, e.t. svn ...
file:///var/svn/RepoName, then where is the code which actually
manipulates the contents of the /v
On Sun, Jul 17, 2011 at 2:07 AM, Andy Canfield wrote:
> The most obvious authorization scheme is that of the host server; if there
> is a user named "andy" on that server with a password "jackel" then I would
> like to simply be able to talk to the subversion server as user named "andy"
> password
On 7/17/2011 2:07 AM, Andy Canfield wrote:
The most obvious authorization scheme is that of the host server; if
there is a user named "andy" on that server with a password "jackel"
then I would like to simply be able to talk to the subversion server as
user named "andy" password "jackel". This is
On Wed, Jul 20, 2011 at 05:22:57PM +0700, Andy Canfield wrote:
> One quirk is that if he URL specifies direct access, e.t. svn ...
> file:///var/svn/RepoName, then where is the code which actually
> manipulates the contents of the /var/svn/RepoName directory? It must
> be hidden in svn itself, or p
On 07/20/2011 12:14 PM, Nico Kadel-Garcia wrote:
On Tue, Jul 19, 2011 at 10:30 PM, Andy Canfield
wrote:
For example, I am on a Linux box named Lenny, logged in as 'andy'. I can ssh
to hk.pimco.mobi as user 'andy', password 'psuedo'. But I don't want to.
Instead, I would like to run the comm
On Tue, Jul 19, 2011 at 10:30 PM, Andy Canfield
wrote:
> For example, I am on a Linux box named Lenny, logged in as 'andy'. I can ssh
> to hk.pimco.mobi as user 'andy', password 'psuedo'. But I don't want to.
> Instead, I would like to run the command:
> svn ... http://hk.pimco.mobi/svn/RepoNa
On 7/19/11 9:30 PM, Andy Canfield wrote:
For example, I am on a Linux box named Lenny, logged in as 'andy'. I can ssh to
hk.pimco.mobi as user 'andy', password 'psuedo'. But I don't want to. Instead, I
would like to run the command:
svn ... http://hk.pimco.mobi/svn/RepoName --username=andy --pas
> -Original Message-
> From: Andy Canfield [mailto:andy.canfi...@pimco.mobi]
> Sent: woensdag 20 juli 2011 4:31
> To: Nico Kadel-Garcia
> Cc: Bob Archer; users@subversion.apache.org
> Subject: Re: Subversion: existing users
>
>
>
> On 07/20/2011 05:24 AM, N
On 07/20/2011 05:24 AM, Nico Kadel-Garcia wrote:
On Tue, Jul 19, 2011 at 12:16 PM, Bob Archer wrote:
The most obvious authorization scheme is that of the host server;
if
there is a user named "andy" on that server with a password
"jackel"
then I would like to simply be able to talk to the sub
On Tue, Jul 19, 2011 at 12:16 PM, Bob Archer wrote:
>> The most obvious authorization scheme is that of the host server;
>> if
>> there is a user named "andy" on that server with a password
>> "jackel"
>> then I would like to simply be able to talk to the subversion
>> server as
>> user named "and
> The most obvious authorization scheme is that of the host server;
> if
> there is a user named "andy" on that server with a password
> "jackel"
> then I would like to simply be able to talk to the subversion
> server as
> user named "andy" password "jackel". This is how ssh and sftp work.
> But
>
On Sun, Jul 17, 2011 at 07:36, Andy Levy wrote:
>
> On Jul 17, 2011 5:02 AM, "Andy Canfield" wrote:
>>
>> The most obvious authorization scheme is that of the host server; if there
>> is a user named "andy" on that server with a password "jackel" then I would
>> like to simply be able to talk to
On Jul 17, 2011 5:02 AM, "Andy Canfield" wrote:
>
> The most obvious authorization scheme is that of the host server; if there
is a user named "andy" on that server with a password "jackel" then I would
like to simply be able to talk to the subversion server as user named "andy"
password "jackel".
28 matches
Mail list logo
