This document details the installation process for the alpha release of the Rover toolkit. There are three sections:
This section lists the operating systems and software requirements for installing and using the Rover toolkit.
The Rover client and server applications should build and execute on most POSIX-compliant UNIX platforms. They have been tested on a variety of platforms, including SunOS (4.1.3_U1), Ultrix (4.3), and Linux (Slackware 3.0/1.3.74 and RedHat 4.2/2.0.30), and OpenBSD (2.1). Automatic detection of network interfaces is available only with the Linux operating system.
The forked Rover server should be compatible with most web servers and has been tested with NCSA's and Apache's httpd servers. Please inform the Rover developers of any incompatibilities.
Note: If the client machine's operating system supports shared libraries (e.g., Linux), you will need Tcl and Tk shared libraries. To reduce transmission time, cache size, and memory usage, Rover client applications may be compiled with dynamic linking on those operating systems that support it. The toolkit libraries are always statically linked.
This section lists the locations of the source code for the toolkit. The Rover toolkit source code and documentation is covered by a copyright notice. Please read the notice before downloading the code.
The developer installation process requires login access or remote NFS mount access to the Rover source CVS repository. If you do not have such access, you should follow the user instructions.
The source code is stored as gzip-compressed tar archive files. Download the code from the following URLs:
The Rover source CVS repository uses CVS (http://www.loria.fr/~molli/cvs-index.html) for source code version control. You will need at least version 1.7 (available from ftp://prep.ai.mit.edu:/pub/gnu). A local quick start guide to CVS commands can be found on this page.
The CVS syntax for checking out modules is: cvs checkout module names
Note: A CVS checkout will fail if the target directory already exists and is not a CVS directory. For example, if you checkout and build the server source code before checking out the server RDOs, the server RDO checkout will fail, since building the source code will create the cgi-bin/rover directory. Thus, it is important to carefully follow the installation and build order listed below.
The CVSROOT environment variable specifies the location of the primary CVS repository, currently pdos.lcs.mit.edu . The source repository supports three access methods: ssh, Kerberos rsh, and NFS access. The most desired access method ssh. NFS access is not recommended.
The server files are the files that are required to install a Rover server. The client files are the files that are required to install a Rover client.
Important Notes:
The Rover documentation should be installed under the httpd server's html directory (usually specified by the httpd server's DocumentRoot variable).
The Rover server RDOs and libraries should be installed under the httpd server's cgi-bin directory (usually specified by the httpd server's ScriptAlias variable).
The Rover server source code should be installed under the httpd server's cgi-src directory.
PRIVATE char *RoverClientACL[] = { "adj", "candea", "dean", "josh", "kaashoek", NULL };The list must be terminated by a NULL entry.
char *RoverRoot[] = { "/usr/local/etc/httpd/cgi-bin/rover", "/u3/httpd/cgi-bin/rover", "/u1/httpd/cgi-bin/rover", "/home/httpd/cgi-bin/rover", ".", NULL };The list must be terminated by a NULL entry.
webcache: |ScriptAlias/rover/rmcacheshell webserv: |ScriptAlias/rover/rmgateshellThis method assumes that you are using sendmail for mail delivery. On some platforms, it may be necessary to execute newaliases to rebuild the aliases database.
The Rover access manager and client applications may be installed in any directory.
The Rover common code consists of directories containing the source code for the Zlib compression library and the common server and client code. For client and server or server-only installations the code should be installed in the server source code directory. For client-only installations, the should be installed in the client source code directory