4. Installing the Software

(Much of this section is taken verbatim from the README file in the Taylor UUCP v1.05 sources - it's provided here so I can help you "rtfm" instead of just telling you to do so)

Detailed compilation instructions are in uucp.texi in the sources.

You can grab "known good" conf.h and policy.h files for Linux from the newspak distribution referred to in the "other sources of information" section above. In that case, you can probably go right to typing "make".

4.1 Extracting the compressed sources

To extract a gzip'd tar archive, I do the following:

                gunzip -c filename.tar.z | tar xvf -

               tar -zxvf filename.tgz

4.2 Edit Makefile.in to set installation directories.

Here, I set "prefix" to "/usr" rather than the default of "/usr/local"

4.3 Run "configure"

Type "sh configure".

The configure script will compile a number of test programs to see what is available on your system and will calculate many things.

The configure script will create conf.h from conf.h.in and Makefile from Makefile.in. It will also create config.status, which is a shell script which actually creates the files.

• Rather than editing the Makefile.in file in the sources as indicated above, you can get the same effect by:

          "configure --prefix=/usr/lib"
  

4.4 Configure the future setup of the software

Examine conf.h and Makefile to make sure they're right.

I took the defaults

Edit policy.h for your local system.

• - set the type of lockfiles you want (HAVE_HDB_LOCKFILES)
• - set the type of config files you want built in (HAVE_TAYLOR_CONFIG, HAVE_V2_CONFIG, HAVE_HDB_CONFIG)
• - set the type of spool directory structure you want (SPOOLDIR_HDB)
• - set the type of logging you want (HAVE_HDB_LOGGING)
• - set the default search path for commands (I added /usr/local/bin to mine)

4.5 Compile and install the software

• Type "make".
• Use "uuchk | more" to check configuration files. You can use "uuconv" to convert between configuration file formats.
• Type "make install" to install.

4.6 Set up the config files

I'd recommend you start by taking the attached known-good config files for HDB mode and installing them.

• Make sure that the Permissions file indicates exactly where rmail and rnews are to be found if you put them anywhere other than in the path you specified in policy.h
• Make sure that your Devices files matches the actual location of your modem (cua1=COM2 in the examples)
• Edit the Systems file to set up the system(s) you talk to with their speed, phone number, username, and password. *PROTECT THIS FILE AGAINST WORLD READ*
• Set up the Permissions file and add a set of lines for each site you talk to. For security reasons, it's recommended to make sure they each have a separate account (if you allow dialin) and home directory so you can track things.

4.7 Give it a try

        /usr/lib/uucp/uucico -r 1 -x 9 -s remote_system_name

The -x 9 will have maximum debugging information written to the /usr/spool/uucp/.Admin/audit.local file for help in initial setup.

I normally run -x 4 here since that level logs details that help me with login problems. Obviously, this contains cleartext information from your Systems file (account/password) so protect it against world-read.

• from Pierre.Beyssac@emeraude.syseca.fr Taylor has more logging levels. Use -x all to get the highest level possible. Also, do a "tail -f /usr/spool/uucp/.Admin/audit.local" while debugging to watch things happen on the fly.

4.8 It doesn't work - now what ?

In general, you can refer to the documentation mentioned above if things don't work. You can also refer to your more experienced UUCP neighbors for help. Usually, it's something like a typo anyway.