fsfs

一、yum安装subversion 1. 安装 subversion yum install subversion 2. 查看安装版本，检查安装是否成功 svnserve --version 3. 查看安装位置 rpm -ql subversion 二、创建版本库 1. 创建用于存放版本库的目录 mkdir -p /www/sdb1/subversion 2. 创建svn版本库 svnadmin create /www/sdb1/subversion 3. 创建完后，版本库目录下会生成一些文件，进入conf目录下 conf目录中authz文件是权限控制文件； conf目录中passwd是帐号密码文件； conf目录中svnserve.conf是SVN服务配置文件 　　4. 修改passwd文件，加入用户，格式就是“用户名=密码”，如： admin = 123 　　5. 修改authz文件，加入用户权限： 　　　　[/] 　　　　admin = rw 　　　这就表示admin用户对版本库根目录有读写权限（即最高权限了），权限配置方式在authz文件注释中有详细说明 　　6. svnserve.conf里面常用的配置有设置匿名用户（默认可读）、授权用户（默认读写）的读写权限，以及指定账号文件（默认passwd）、权限文件（默认authz）的路径等 ### This file

We're in the process of moving servers and one of the last items is moving over the svn repositories. There are about 10 gigs of various svn repositories. They were created using this command: svnadmin create --fs-type fsfs Server A(original) has svn 1.4 while Server B(target) has svn 1.6. My thought was to use rsync to migrate the whole set of repositories (they are all in 1 folder on the server), but I am worried that some things might either not get migrated or I need special switches for rsync for this to work. Most online tutorials only talk about moving 1 repository at a time, for

How can I determine current version of my repository to see if I need to upgrade it (svnadmin upgrade)? In reality I'm hosting SVN with 3rd party and I want to find out if I need to ask them to upgrade my repos or not. I'm asking since 1.5 server will keep repo version at 1.4, unless I miss something? Have a look at <REPO>/db/format . After upgrading to 1.5 format, my format file shows: 3 layout sharded 1000 Before it used to be: 2 Take the http or https link to your repository and cut & paste it into a browser. The Subversion repository server version appears in the footer by default. Powered

I read the subversion book and it is clear to me that subversion does not store individual files but only deltas in order to minimize disk space. Subversion also does the same with binary files as well (this used to be a huge weakness of CVS). However I do not understand the exact mechanism. When I commit a file what happens? Subversion stores only the diff (and already has the old version) Subversion deletes the previous version, stores the new file intact and creates a reverse diff in order to "re-create" the old version if needed. Something else that I haven't thought of. The first case

My project is currently using a svn repository which gains several hundred new revisions per day. The repository resides on a Win2k3-server and is served through Apache/mod_dav_svn. I now fear that over time the performance will degrade due to too many revisions. Is this fear reasonable? We are already planning to upgrade to 1.5, so having thousands of files in one directory will not be a problem in the long term. Subversion on stores the delta (differences), between 2 revisions, so this helps saving a LOT of space, specially if you only commit code (text) and no binaries (images and docs).