head	1.5;
access;
symbols
	NUTS333:1.5
	NUTS332:1.4
	NUTS331:1.3
	NUTS330:1.2
	NUTS321:1.1
	NUTS320:1.1;
locks; strict;
comment	@# @;


1.5
date	96.12.10.06.13.47;	author kcozens;	state Exp;
branches;
next	1.4;

1.4
date	96.12.10.05.08.18;	author kcozens;	state Exp;
branches;
next	1.3;

1.3
date	96.12.09.07.48.30;	author kcozens;	state Exp;
branches;
next	1.2;

1.2
date	96.12.09.06.36.16;	author kcozens;	state Release;
branches;
next	1.1;

1.1
date	96.07.23.15.54.31;	author kcozens;	state Exp;
branches;
next	;


desc
@This file provides some information on compiling and running the talker.
@


1.5
log
@Updated the version number of the file in the compile commands listed.
@
text
@*** Compiling and running the talker ***

I had thought of dividing this version of NUTS up into separate source files
then compiling and linking them together using a makefile but in the end
I decided that it there was very little point as the code isn't that large
and once its compiled its unlikely to be done again unless you decide to
hack it about a bit or move to a different system.
This software was developed in parallel on HP-UX 10.01 using the ANSI compiler 
and Linux 1.2.13 using gcc 2.5.8 so there should be no probs with either of 
these. I have also compiled and run it on SCO 3.2, AIX 3.2 and DYNIX 4.1.3 and 
it seems to work fine though I have not done soak tests on these systems. 

To compile:

Linux & AIX: cc nuts333.c
IRIX & OSF : ditto above?
HP-UX      : cc -Ae nuts333.c  (you need the ANSI compiler)
SCO 3.2    : cc nuts333.c -lsocket -lcrypt_i  
DYNIX 4    : cc nuts333.c -lsocket -lnsl
Solaris    : cc -lsocket -lnsl nuts333.c  (not guaranteed to work)
SunOS 4    : dont even bother unless you have gcc

Running...

The talker comes with a config file ready made (datafiles/config) which will
be a good starting point for you. There are some network addresses in there
but they are more of a guide as to how to set up talker links rather than
being genuine links themselves. 
	To start the talker just type "go" and it will boot and automatically 
run itself in the background. All its actions are written to the syslog file. 
To log in you then just telnet to port 7000 and log in as "fred" with the 
password "test" as this is an account set up with GOD status. The "go" script
assumes the executable is called a.out.

I have included a 2nd config file called config2. This is so you can set up
another talker (by copying the files from this current one) and have them
link together. The only file that need to be different is the config file.
Move config2 into the 2nd datafiles directory as config and run the 2nd 
talker.

@


1.4
log
@Minor updates regarding compiling on other operating systems.
@
text
@d15 1
a15 1
Linux & AIX: cc nuts332.c
d17 4
a20 4
HP-UX      : cc -Ae nuts332.c  (you need the ANSI compiler)
SCO 3.2    : cc nuts332.c -lsocket -lcrypt_i  
DYNIX 4    : cc nuts332.c -lsocket -lnsl
Solaris    : cc -lsocket -lnsl nuts332.c  (not guaranteed to work)
@


1.3
log
@Updated the information as to which operating systems the code has been
(or can be) compiled to run under.
@
text
@d10 2
a11 3
these. I have also compiled and run it on SCO 3.2 and AIX 3.2 and it seems to
work fine though I have not done soak tests on these systems. The talker should
also compile fine OSF/1.
d15 6
a20 5
Linux & AIX: cc nuts331.c
IRIX       : ditto above?
HP-UX      : cc -Ae nuts331.c  (you need the ANSI compiler)
SCO 3.2    : cc nuts331.c -lsocket -lcrypt_i  (put the .c file first!)
Solaris    : cc -lsocket -lnsl nuts331.c  (not guaranteed to work)
@


1.2
log
@Some minor updates re: compiling for HPUX or SunOS.
@
text
@d10 12
a21 8
these. The talker should also compile fine on AIX and OSF/1 (I hope) though 
apparently there have been problems on certain versions of Solaris/SunOS in 
that it doesnt load up the sockets library. See below.
	Generally you'll just need to enter "cc nuts330.c" to compile though
for HP-UX you need to type "cc -Ae nuts330.c" and for SunOS you may need
to enter "cc -lsocket -lnsl nuts330.c".
Please note that you NEED the ANSI compiler for HP-UX, the bundled K&R one
is useless. You'll soon know if you don't have it when you try to compile :)
@


1.1
log
@Initial revision
@
text
@d8 8
a15 6
This particular version of the software was developed in parallel on 
HP-UX 10.01 using the ANSI compiler and Linux 1.2.13 using gcc 2.5.8 so 
there should be no probs with either of these. The talker should also compile
fine on AIX and OSF/1 (I hope).
	Generally you'll just need to enter "cc nuts320.c" to compile though
for HP-UX you need to type "cc -Ae nuts320.c". 
d17 1
a17 1
is useless.
d21 1
a21 1
The talker comes with a config file ready made (datadir/config) which will
@
