NET_SCCS(1)                                                      NET_SCCS(1)

INSTALLATION
   
   Ok, this has completely changed since 05/01/98.  It's still an
   entirely manual process, and will stay as such untill we 
   approach a more complete/stable version of the software.

   Please note that you will have to have the following software packages
   to take advantage of this system:

     JDK 1.1.5 or higher 
       You can get this for Linux from http://www.blackdown.org
       You can get this for Windows, or for Solaris from Sun's 
       web site:  http://www.sun.com  I don't know where you can 
       get the JDK for other platforms, try searching the net.
       This is only needed for the client machines.

     RCS 
       Revision Control System, this is installed by default on
       most Linux systems.  You can obtain RCS from any free software
       archive, such as ftp.cdrom.com, or gatekeeper.dec.com
       This is only needed for the server.

     CGI.pm  
       This is the standard CGI perl module, it should come with the 
       standard distribution of perl, but it might not if you got
       perl with a commerical operating system (I know this to be
       true of HP-UX).  If you do not have this, you can obtain it
       from any CPAN mirror.  You can obtain a list of CPAN mirrors
       from:  http://www.perl.org
       This is only needed for the server.

   The system is kinda dependant on where it's installed.  You'll
   need to create a subdirectory named net_sccs under your cgi-bin 
   directory on the server.  You should also create a net_sccs
   directory under your html directory.  If your web server is 
   installed in /home/httpd, then you should create the following
   two directories:
   
       /home/httpd/cgi-bin/net_sccs
       /home/httpd/html/net_sccs

   Extract the source archive into /home/httpd/html/net_sccs, and 
   copy the cgi scripts from the net_sccs/cgi directory into 
   /home/httpd/cgi-bin/net_sccs.

   Set the executable bits on rb_sccs.cgi.  Also, make sure the
   web server has write access to the repository directory, as 
   that is where it will end up storing all of the archived
   files.

   For the local installation, you'll need to build the Java
   front end in the cmdline directory.  If you have the 
   jdk-1.1.5 installed, and the java interpreter, and comipler
   on your path, you should be able to just execute make from
   that directory.


CONFIGURATION

   There are two configuration files used by the system.  One is 
   used by the server, and is expected to be:
     
      /etc/net_sccs.conf

   The client side conf file is exptected to be found in one of
   the following places:  the user's home directory, the current
   directory, or c:\ [assuming it's a dos based system].

   net_sccs.conf supports the following directives:

     language
       This tells the server scripts which language files to use. 
       Currently this is not implemented.
  
     net_sccs_cgi_dir
       This tells the cgi scripts where they are installed.
  
     net_sccs_repository
       This tells the cgi scripts where the source code repository
       is.  

     add_users
     get_users
     checkout_users
     checkin_users
       These are a 'light' implementation of security, they are comma
       seperated lists of usernames which list what users are allowed
       to do.  If a user's name appears in the list for one of these
       then they are allowed to perform the given action.  If their
       name does not appear, then they can't perform the action.
  
   The client side config file supports the following directives:
     
     language
       This tells the client what language to use when displaying
       output.  Currently this is not implemented.

     net_sccs_host
       The client will attempt all communications with this host.
       It will expect at least the following to be present on the
       host specified:  
         /cgi-bin/net_sccs/net_sccs.cgi
         /net_sccs/msgs/[language].net_sccs.strings.txt
         /net_sccs/msgs/[language].net_sccs.help.txt

     default_user
       This frees the user from having to supply a user name every time
       the command line utility is executed.  Please note that there is
       currently no user level security, the username get's passed
       to net_sccs, but is not used.

     default_password
       Same as default_user -- it gets passed to net_sccs, but is not used
       by the system.  If you use this, make sure your .net_sccs file is 
       only readable by you (0400).

     default_path
       As with default_user, this frees the user from having to 
       enter a path for every command.  


   Once you have all these things in place, you can test the system.
   To test the system, run one of the command line utilities, and 
   ask it for help.  

     java get -h

   If it displays the help text, you should be good to go.  If it 
   doesn't, let me know and I'll try to help you figure out what's
   wrong.  For information on using the system, see the documentation
   under doc/