Some fast notes:
cvs -d /usr/local/cvsroot init. This creates the directory CVSROOT under /usr/local/cvsroot. Covered on page 17 on the manual, section 4.5.
cvsUsername:encryptedPassword:effectiveUsernameand place it in the CVSROOT directory, eg:
testuser:46hLKUa/MFVOE:mcgredo. This allows someone to use (say) jCVS to log into the server, supply the username testuser and the password, and operate on the server machine with the priviliges of the unix user mcgredo. Presumably mcgredo belongs to the group that has access to the directories in question, eg cvs.
cvs import -m "Initial sources" mil/navy/nps/dis djv start. This checks in the directory, makes entries in CVSROOT, and creates the ,v files.
java -classpath ./jcvs.jar;c:/jdk1.2.2/lib/classes.zip CVSApplication. The application itself lives in the jar file, and the classes.zip file is where all the jdk distribution classes live.
-r tagName". This will check out all files that have had that tag applied. By default, the initial checkin supplied a tag of "start" to all files, so you can checkout the original version of the module (including any files that may have been deleted from the module.)