Installation for Discuss: Prerequisites: Discuss, as distributed, assumes the presence of Kerberos, Project Athena's authentication system, and Zephyr, Project Athena's notification system. Discuss comes with the SIPB/IS et (error table) and ss (command subsystem) libraries. Kerberos is available for U.S. sites via anonymous FTP to ATHENA-DIST.MIT.EDU (18.71.0.38). Discuss uses Kerberos to authenticate network users. Without Kerberos, you can only operate Discuss within a single machine. Zephyr is not available at the time of release. The Discuss server uses Zephyr to notify users of new transactions in meetings. Build: 1. This release of Discuss is configured to use Imakefiles to generate Makefiles. All hardcoded pathnames and destinations are defined in source/config/site.def. You should change the definitions as appropriate. These fields are documented in the file. Depending on your machine type, you may need to get an Imake configuration file from the X11R4 distribution (e.g., sun.cf) 2. Compile Discuss by running 'make' in this top-level directory. 3. If running Discuss on the network, you should register the discuss service by adding the following line to /etc/services on the appropriate machines (client & server): discuss 2100/tcp # Networked conferencing. 4. Server installation: Create a user "discuss", with no password, and no shell. Discuss meetings will be owned by this user. Here is a sample password entry: discuss:NOPASSWORD:32000:5002:Discuss System,,,,:/usr/spool/discuss:/bin/csh On a discuss server, you can install discuss by running 'make install'. This will put the server programs in SERVERDIR. The discussd program is used by inetd to serve discuss connections; disserve is a setuid program used as a subprocess of normal discuss clients on the same machine (as configured in config.h). Add the following line to inetd.conf for inetd to serve discuss connections: discuss stream tcp nowait discuss /usr/athena/etc/discussd discussd Create a directory /usr/spool/discuss, owned by discuss, mode 700 (rwx------), or mode 755 (rwxr-xr-x). Obtain a discuss srvtab from your kerberos administrator. This is the shared key between Kerberos and the discuss server. The principal name should be "discuss", and the instance should be the machine-name in lowercase. For instance, the discuss server on the machine Charon would use the Kerberos name discuss.charon. Install the srvtab as /usr/spool/discuss/srvtab, mode 400 (r--------), owned by the discuss user. Follow the directions in the Discuss adminstrators guide (doc/admin), to create Discuss meetings on the server. 5. Client installation. Verify that INFODIR & DESTDIR are properly set in site.def 'make install' in the client, mclient and dsgrep directories. This will put the client programs (discuss, pmtg, mkds, crmtgs, rmds, create_mtg_dir, dsmail, dspipe) and client scripts (dsc_setup) in DESTDIR, and the info files into INFODIR. 6. If installing the emacs discuss client, you should look in source/edsc. discuss.el should be edited so that discuss-pathname has the pathname for the edsc program. Install discuss.el & discuss-enter.el somewhere in your emacs load-path, byte-compile them if you want, and install edsc in the proper place. 7. Examine the administrator's guide (doc/admin) to see how to create new Discuss meetings. Once you have created some meetings, you may wish to change dsc_setup (source/mclient/dsc_setup.sh) to set up your own initial set of meetings. The installation has not been exhaustively tested on that many platforms; if you run into any troubles, let us know, so we can fix the distribution. Thank you. Good luck.