cvs should be installed. If not, go to
http://www.cvshome.org/ and download the package. You will most likely have to compile directly from its source code.
cvs -d
server:anonymous@yourhost.com:/your/cvs/directory login
Your CVSs server administrator will have to tell you how to login to their CVS repository. Usually for public read-only access, the username will be guest or anonymous and the password is NULL or blank.
To actually check out a module now, you will have to run this command:
cvs -zX -d
server:anonymous@yourhost.com:/your/cvs/directory co MODULENAME
the -d parameter can be set in an environment variable (CVSROOT) so that you do not have to type it out every time. CVSEDITOR can be used to set the editor you will use when committing a change to the repository.
This being said, if you're developing with CVS or plan to have write access to a repository - RUN THE FUCK AWAY FROM IT. I'm not kidding you. You will have a nervous breakdown and go postal trying to deal with it. It *will* screw up eventually and you *will* want to fuck with its history and rcs files etc etc at some point in time. Maybe not you, but the system will fuck something up and you'll lose valuable history. For another example, You cannot version directories (iirc), and if you move a file from one directory into another, you will lose history (iirc).
Encourage your CVS system administrator to look into Subversion, more commonly known as svn.
- It uses a Berkeley database backend (ie, you can read it with any Berkeley utilities out there) for its information storage. They are planning an SQL end, but far into the future.
- It has hot-copy backup.
- It looks and acts as much as CVS as possible (because the developers want people to easily migrate from CVS).
- It has a cvs2svn migration utility.
- To date, no one (not even the developers) have lost any Subversion repositories. I myself have been using it since 0.10 with nary an issue.
- Can move directories and branches etc with no problem (you will find this an issue if you continue to use CVS).
</radical conversion rant>
As for your AV for Linux? You can use clamav ... but then again, why would you be worried about viruses in Linux? All of them require root priveleges and you wouldn't be stupid enough to run untrusted binaries (of which the virus author will most likely tell you it *requires* root priveledges to run, which any good developer will tell you is not absolutely neccessary for most applications).
Believe it or not, a lot of people use ClamAV to run their e-mail through a virus scanner before it gets passed onto Windows clients.
