Server
------

To install the server without reading any instructions, look in the
configs directory (in qi).  Change the file "defaults" to include your
domain name, desired directories, and features.  Then look for a config
file for your system.  Finally, in the main qi dir, type: 

Configure systemtype
make install

Finally, build the database (see 1.3, below), and modify your inetd.conf
file and your services files to reference the server.  Here are sample
entries: 

In services:
ns                  105/tcp

If you are using NIS, run ypmake after modifying services.

In inetd.conf:
ns                  stream tcp nowait root   /usr/local/lib/cso/qi qi -d -t30

After modifying inetd.conf, make the inetd reload inetd.conf:

inetd -c

Client
------

Unix: The Unix client comes as part of the server package.  The easiest
way to install it is to do it as part of the server package, above.  The
Configure script will automatically generate a Makefile for your system,
and will make and install the ph client.  If for some reason you cannot
make the entire qi package, here are the minimal steps for making the
client: 

Look in the configs directory (in qi).  Change the file "defaults" to
include your domain name, desired directories, and features.  Then look
for a config file for your system.  Finally, in the main qi dir, type: 

Configure systemtype

Next, make the api library used by ph:
cd api
make

Finally, go back to the qi dir, cd to the ph dir, and do a make:

cd ..
cd ph
make

If all goes well, finish with:
make install

Note that the client distribution (a separate from the entire qi
distribution), includes a Makefile already generated for a system at uiuc.
While it is possible to edit this Makefile (despite the "Do not edit"
warning at the top of the file), it is much easier to make ph as a part of
qi. 

Other clients:

The ph distribution comes with clients for the following systems:

a. CMS, requires TCP/IP for VM Version 1.2 or later IBM C/370 Compiler and
   Runtime library (Version 1.2.0)
b. DOS, with both source and executable, requires MS-DOS, PC/TCP by FTP
   Software
c. MAC, requires MacTCP
d. Next
e. PC-NFS version (for MS-DOS and SUN's PC-NFS)
f. VM, in Pascal
g. VMS 5.3 with Wollongong WIN/TCP 5.1
h. Windows (with winsock)
i. X-Windows

Some other clients not part of the distribution:

uwho (pronounced "you-who") is another people-finding front end program
that was created by Daniel Kegel (dank@alumni.caltech.edu), because whois
seemed difficult to use- you had to know what the hostname of the whois
server was, which is a detail that users shouldn't have to know. 

uwho is a front end to several white pages services (currently, whois,
ph, and KIS). It accepts a name and partial organization name, does a
search for matching organizations, runs whois, ph, or KIS queries (as
appropriate) in parallel, then shows the user the results. It is
powerful simply because it accesses a continually updated list of white
pages servers [i.e., it searches current information, not its "own list
of users"], so its power will grow as more [user-information] servers
come online.

Uwho is written in C and runs under Unix, VMS, NT, and MS-DOS. For more
information, consult uwho.doc. The latest version is uwho218b.tar.Z or
uwho218b.zip and can be browsed as individual files. 

Or, if you don't have Web access, everything can be had at
    ftp://alumni.caltech.edu/pub/dank/

uwho2html, a WWW front end to uwho, is also available.


Most gopher browsers support PH queries
Many World-Wide-Web browsers
Some Mail packages (notably Eudora)


Other Vax/VMS clients available via anonymous ftp:
  UCX:           esa.lanl.gov
  UCX:           noc.macc.wisc.edu
  Multinet:      icaen.llnl.gov
  UCX & Mulinet: ftp.ceri.memst.edu