Computational infrastructure

Setting up SSH with public key authentication
Generate a private/public key pair - it gets written to ~/.ssh/id_dsa and ~/.ssh/
    ssh-keygen -d
On the machine you want to login on, copy your public key to ~/.ssh/authorized_keys2.

sshd will let anybody who has the private key for the public keys in ~/.ssh/authorized_keys2 login without password authentication. So make sure you keep your private key private!

    cd .ssh
    cp authorized_keys2
Setting up the source tree
Once you've got your account for TP1, you can check out the current code from CVS. Add to your login script (.bashrc/.cshrc/whatever):
    export CVS_RSH=ssh
    setenv CVS_RSH ssh
respectively. All sources should be located under ~/src:
    mkdir src
    cd src
Now, you can check out the latest version from the CVS repository:
    cvs -d checkout makeinclude
    cvs -d checkout util
    cvs -d checkout Matrix
    cvs -d checkout numlib
To setup the basic framework, enter the following directories:
In each of them, type
    make install
This will build the libraries and install them to ~/include and ~/lib/[arch], respectively.

You can have a look at the examples in ~/src/Matrix/tests to get an impression of the matrix classes.

Basic CVS
    cvs -d  [cvsroot] checkout [modulename]
Check out a local copy of the module [modulename].
    cvs update 
Update your local copy with the latest changes from the repository.
    cvs commit
Commit your local changes to the repository, i.e your version will be the latest official version others get upon cvs checkout / update.
    cvs add [filename]
Schedule a newly created local file for addition to the repository. Upon the next cvs commit, the action is taken.
    cvs rm [filename]
Schedule a newly created local file for removal from the repository. Upon the next cvs commit, the action is taken. Old version are still accessible via the repository, even if the current version was removed.

For more information:

Kai Germaschewski
Last modified: Fri Nov 9 13:49:30 CET 2001