[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

A few book comments

From: Tobias Ringstrom <tobias_at_ringstrom.mine.nu>
Date: 2004-01-14 15:10:24 CET

[I'm not sure if docs/book/REVIEW is for the authors only, so I send it
to the list instead.]

Chapter 5:

The section on repository recovery could use some text about how to
recover a repository which has permission problems, i.e. describe an
chown/chmod operation. A link to the "Using Multiple Servers" section
would obviously be appropriate near that description.

Chapter 6:

* The name of the section is "Using Multiple Servers", but the issues
discussed are important even if you don't have a server at all (i.e.
file://) or if you use tunnel mode.

* The paragraph that begins with "The most common problem..." says that
you may need to put all users in a common group and make sure that the
repository is wholly owned by that group and that the umask must be
correct. It does not explain that you will need to set the group set-id
bit on the directories, which is a very important step, i.e.

        find repos -type d | xargs chmod g+s

* The sample svn wrapper script is missing the "$@" argument to the svn

And now some humble ideas:

* It would be nice to have an example of using ssh port forwarding as
well, i.e. to run

        ssh -L 10000:localhost:3690 user@remote.host

in one window, and then connect to the svnserve on remote.host using

        svn list svn://localhost:10000/project1

This method is much faster than svn+ssh, and you only need to enter the
ssh password more than once.

* It would be helpful to mention that it's possible to use ssh-agent to
not have to enter the SSH password on every connection.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 14 15:11:00 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.