%general-entities; ]> For editors, access is slightly more complicated. You first of all need to generate an ssh key-pair. You then need to upload your public key into your ~/.ssh directory on belgarath. To generate the keys run: ssh-keygen -t dsa When prompted as to where to save them, it's probably best to leave them in .ssh (as id_dsa and id_dsa.pub) unless you already have ssh keys there. When prompted for a passphrase just press enter (unless you want to have to give the phrase every time you perform a subversion operation. But, since the same passphrase will be used when you log in to belgarath over ssh, it may be advisable to have some security in place. Having generated your keys, upload ~/.ssh/id_dsa.pub to belgarath and move it to ~/.ssh/authorized_keys2 on belgarath. (Your local copy of id_dsa and id_dsa.pub should remain untouched by this.) Make sure that the ~/.ssh directory on belgarath is mode 700: chmod -R 700 ~/.ssh Once you have this setup, try to checkout the latest LFS book revision by running: svn checkout svn+ssh://svn.linuxfromscratch.org/LFS/trunk/BOOK lfs-trunk If this works, you'll checkout a copy of the current book to lfs-trunk and you will have your own local working copy. You will also have write access so from now on be extra careful, but note that no changes will be made until you issue a svn commit command. The above is fine for working in trunk, and you can checkout an individual branch in a similar manner. But, merging changes between branches is much easier if you check out the whole tree by running: svn checkout svn+ssh://svn.linuxfromscratch.org/LFS LFS The drawback to checking out the whole tree is that you will currently get about 102M of data instead of 5M. As with anonymous access, you can update your local copy by simply cd'ing into the LFS directory and running: svn update