- Key generation (skip ssh-keygen if you already have a key)
- Linux:
- ssh-keygen -t dsa
- suggestion: use an empty pass phrase (rerun if you used a non-empty one)
- E-mail your adviser your public key file ~/.ssh/id_dsa.pub in an ATTACHMENT (not inline)!
- You can install the same public-private key pairs on multiple machines just by copying the respective keys (as intrinsic machine names are not checked). This way, only one key needs to be installed for you.
- eos/unity:
- add ssh
- ssh-keygen
- E-mail your adviser your public key file ~/.ssh/identify.pub in an ATTACHMENT (not inline)!
- add goodies
- cvs ... (see below)
- Windows:
- Install openssh
cd c:\Program Files\OpenSSH\bin mkpasswd -l -u administrator >> ..\etc\passwd mkgroup -l >> ..\etc\group net start opensshd ssh optout add host? --> yes Control-C at password prompt cd c:\Documents and Settings\%USER% mkdir .ssh cd .ssh ssh-keygen -t dsa - E-mail your adviser your public key file ~/.ssh/id_dsa.pub in
an ATTACHMENT (not inline)!
- Install TortoiseCVS
In WindowsExplorer: cvs->preferences->ssh: c:\Program Files\OpenSSD\bin\ssh.exe checkout: protocol=ext, server=optout, reposi=/home/cvs/cvs, user=unity-id, module=some-directory use Pageant to point to your private key of the ssh protocol
- Install openssh
- Platform agnostic: using Eclipse
- Eclipse download for win32
- CVS under Eclipse
- Add CVS Repository to Eclipse:
- For Location Host, enter optout.csc.ncsu.edu
- For Location Repository path, enter the path of the cvs repository: /home/cvs/cvs
- For Authentication User, put your server account user-id.
- (this step not required due to id_dsa.pub public key) For Authentication Password, put your server account password.
- For Connection Connection Type, select extssh from the drop-down list.
- Check Validate Connection on Finish if it is not already selected.
- Click the Finish button.
- If you want to access the repository from different machines, repeat these above steps for each such machine (N/A for eos/unity).
- Linux:
- CVS setup
- Once you receive a response that you have been added, start using CVS.
- eos/unity:
add ssh
Needs be be done each time you log in. - Add to your ~/.bashrc (or equivalent, e.g., use setenv instead
of export for csh/tcsh):
export CVS_RSH=ssh export CVSROOT=<unity-id›@optout.csc.ncsu.edu:/home/cvs/cvs
- For newer OpenSSH versions, add to your ~/.ssh/config:
PubkeyAcceptedKeyTypes=+ssh-dss
- Go to your project directory: cd ~/projects
- Access existing directories:
- cvs checkout directory-name
- Add your own (new) directory at the top level:
- cvs checkout top
- Create a subdirectory with either your <unity-id›
- cvs add <unity-id›
- cvs commit -m start <unity-id›
- Move all your project source files and subdirectories into this new directory
- Go to your subdirectory: cd <unity-id›
- Add all files: cvs add *
- Commit files: cvs commit -m start
- Trouble shooting:
- cvs [XXX aborted]: reading file: Permission denied: Make sure your files are owned and readable by yourself (and not only by root) -- if only root has access, you'll see this message.
- Killed / takes a long time: use "cvs -t import ..." to observe which files are being checkin in. If a file is too big (to be handled in memory on your local machine), you may have to split it up: split --bytes=80000000 file file.
- Add an entire directory subtree to cvs (assuming the current
directory has already been added and committed):
- find . -type d -print | xargs cvs add
- find . -name CVS -prune -o -type f -print | xargs cvs add
- Import entire directory structure into cvs:
- copy your files into some directory <unity-id›
- cvs import -m "comment" <unity-id› <unity-id› start
- Always run cvs update first before making changes since someone else may have modified files.
- Merging: An update may result in conflicts marked with <<< and >>>. You need to resolve conflicts by hand deciding which version (<<< or >>>) should be included in the file and deleting the other other version.
- Add new files/directories: cvs add file
- Commit changes at the end of each day: cvs commit -m <comment›
- Check edit history: cvs log file
- Check file status: cvs status file
- Check out a directory (but not the files): cvs co -l <directory›
- Example: create your thesis directory
- cvs co -l thesis
- cd thesis
- mkdir <unity-id›
- cvs add <unity-id›
- cvs commit -m start <unity-id›
- cd <unity-id›
- Copy all source files here, then cvs add & commit them.
- Remove last version from cvs: cvs admin -o <revision-number› file
- Lock file: cvs admin -l file
- Lock file: cvs admin -u file
- add file as binary file: cvs add -kb file
- indicate at a later time that file is binary: cvs admin -kb file
- cvs racl student:p -r ALL -d ALL
- cvs racl ALL:n -R -r ALL -d proposals/
- cvs racl student:a -R -r ALL -d proposals/
- after any cvs racl on optout: chmod 644 /home/cvs/cvs/CVSROOT/access
- added to /etc/bashrc on server: export TMPDIR=$HOME (avoids using /tmp before actual commits -- /tmp was overflowing for large-- -- files)
- indicate file extensions for binaries: $(CVSROOT)/CVSROOT/cvswrappers
(for TortoiseCVS: edit TortoiseCVS/Filetypes.config) - undo a remove (manually only): mv Attic/file .
- added cvsacl patch 1.1.0 to cvs 1.11.6 (local copy)