projects / unix-history / blame
| Commit | Line | Data |
|---|---|---|
| d92f211d C |
1 | This directory contains the version of the UNIX XNS/Courier implementation |
| 2 | currently under development by JQJ@CORNELL. It is still a test version. | |
| 3 | This file last updated 31 Dec 1986 (Ed Flint). | |
| 4 | ||
| 5 | To install the XNS Courier package: | |
| 6 | ||
| 7 | 1/ install 4.3BSD, including support for XNS protocols by K. Sklower. | |
| 8 | The Courier system is known to work on VAXes and Gould Powernode | |
| 9 | systems running 4.3BSD. It probably works on a SUN with XNS | |
| 10 | support. Note that it assumes that the routine ns_addr() is in | |
| 11 | /lib/libc; this was not the case for the 4.3BSD Beta distribution. | |
| 12 | 2/ make sure an interface has been enabled for xns e.g.: | |
| 13 | ifconfig en0 ns 2273 (if en0 is connected to | |
| 14 | XNS network number 2273) | |
| 15 | 3/ edit the Makefile in this directory and modify the user-tunable | |
| 16 | parameters CHDEFAULT, DESTDIR, DESTBIN, DESTLIB, DESTINCLUDE and | |
| 17 | DESTCOURIER. At a minimum, CHDEFAULT should be changed to the | |
| 18 | default :domain:organization for the system being installed; the | |
| 19 | remaining parameters will default to appropriate directories | |
| 20 | within the 4.3BSD system. | |
| 21 | 4/ do ``make all'' on this directory. This will build the package | |
| 22 | and deposit the necessary files in the bin, lib, include and | |
| 23 | xnscourier subdirectories. | |
| 24 | A simple ``make'' won't do, since some things require previous | |
| 25 | installation of earlier things. | |
| 26 | 5/ do ``make install'' on this directory. Note that you MUST use | |
| 27 | ``make install'', and will probably need to be logged in as root. | |
| 28 | This will copy the previously made files to the appropriate system | |
| 29 | level directories as specified by the user-tunable parameters in | |
| 30 | the Makefile. | |
| 31 | 6/ edit /etc/rc.local to automatically run | |
| 32 | /usr/new/lib/xnscourier/xnscourierd at system startup. This is the | |
| 33 | daemon that listens for incoming Courier connections. When it | |
| 34 | receives a connection, it looks up the remote program in | |
| 35 | /usr/new/lib/xnscourier/Courierservices and runs that program. | |
| 36 | ||
| 37 | Notes: | |
| 38 | 1/ The file ./morexnslib/ch/clearinghouse.addresses may contain | |
| 39 | the address of a local clearinghouse and a list of the domains | |
| 40 | served. This file will be created during the make; the package | |
| 41 | will build a program called xnsbfs which finds local clearinghouses | |
| 42 | and the output of this program will be used to create | |
| 43 | clearinghouse.addresses, and the result stored as the file | |
| 44 | ./lib/xnscourier/CH.addrs. | |
| 45 | Note that you MUST have a Xerox-provided or compatible (3Com won't | |
| 46 | do) Clearinghouse on your local network. | |
| 47 | 2/ Some programs in this package use the contents of the file | |
| 48 | ./lib/xnscourier/CH.default as a default if no domain | |
| 49 | is specified, e.g. "gaptelnet foo" defaults domain and | |
| 50 | organization on foo based on this file. The file | |
| 51 | ./morexnslib/ch/CH.default is built by the package to contain this | |
| 52 | default value, as specified in CHDEFAULT in the Makefile. | |
| 53 | ||
| 54 | Problems: | |
| 55 | 1/ The compiler is incomplete: it does not handle forward references, | |
| 56 | recursive declarations, constants containing a non-trivial CHOICE, | |
| 57 | or recursive DEPENDencies. | |
| 58 | 2/ The client runtimes are incomplete: they do not correctly handle BDT | |
| 59 | Abort messages; they require a static file (clearinghouse.addresses) | |
| 60 | containing a local Clearinghouse rather than performing an expanding- | |
| 61 | ring search. | |
| 62 | 3/ The server runtimes are incompletely tested. | |
| 63 | 4/ Providing Courier services is quite expensive. In general, at least | |
| 64 | one process per SPP connection is required. | |
| 65 | ||
| 66 | On the other hand, the package is adequate for writing non-trivial Courier | |
| 67 | client and server programs. Of particular note are the example subdirectories | |
| 68 | print, gap, and filing, which contain Courier applications for (1) printing | |
| 69 | an Interpress master on a Xerox printer, (2) telnet (chat, aka GAP) from Unix | |
| 70 | to file servers or from ViewPoint to UNIX, (3) an ftp-like interface to filing, | |
| 71 | allowing a Unix user to store and retrieve files from a Xerox file server and | |
| 72 | a XDE FileTool compatible Unix file service. | |
| 73 | ||
| 74 | Note that in order to use XDE Chat, ViewPoint remote system administration or | |
| 75 | FileTool to your UNIX system you will need to register the UNIX system with | |
| 76 | the Xerox Clearinghouse. To do so, use the program registerhost contained on | |
| 77 | the examples/ch directory. |