head	1.11;
access;
symbols
	NUTS333:1.11
	NUTS332:1.10
	NUTS331:1.9
	NUTS330:1.8
	NUTS321:1.7
	NUTS320:1.6
	NUTS312:1.5
	NUTS311:1.4
	NUTS310:1.3
	NUTS300:1.2
	NUTS300a:1.1;
locks; strict;
comment	@# @;


1.11
date	96.12.10.06.17.51;	author kcozens;	state Exp;
branches;
next	1.10;

1.10
date	96.12.10.05.22.52;	author kcozens;	state Exp;
branches;
next	1.9;

1.9
date	96.12.09.07.53.54;	author kcozens;	state Exp;
branches;
next	1.8;

1.8
date	96.12.09.06.18.33;	author kcozens;	state Release;
branches;
next	1.7;

1.7
date	96.07.23.16.44.55;	author kcozens;	state Exp;
branches;
next	1.6;

1.6
date	96.07.23.15.45.56;	author kcozens;	state Exp;
branches;
next	1.5;

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

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

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

1.2
date	96.07.23.13.51.49;	author kcozens;	state Exp;
branches;
next	1.1;

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


desc
@This file was updated to provide information on the state of NUTS since the
3.1.2 release. This is supposedly the last release of code from Neil.
@


1.11
log
@A note was added stating this is supposed to be the last version of NUTS.
A few other minor changes were also made.
@
text
@*** README for triple three (3.3.3 :) ***

Read the DOCS/diffs file for update information.

Welcome to NUTS if you're a first time user. Hopefully you'll find it a
simple system to use thanks to the helpfiles and the documentation , if not
then please feel free to email me at the address at the end of this file.
Before I continue though I must stress that I WILL NOT SORT OUT BUGS OF YOUR
OWN MAKING OR WRITE CODE FOR YOU! If you write your own code or alter my
code and fuck it up thats your problem, I have my own projects to do and I
am *not* interested in sorting out yours. I've had one too many emails from
people asking me to sort out the mess they've made and I'm getting rather sick 
of it. However, despite me putting this request in the 3.3.1 docs some people 
have seen fit to ignore it so heres an added incentive: mail me about your cock
ups and not only will I not reply to the mail but I will keep a note of your 
email address and I will not reply to *any* mails you send me even if its about
problems with *my* code. Its your choice. 

I know I've said this before but this time I really mean it. This is the final
version of NUTS 3. I have ideas in mind for a version 4 but thats years away
so in the meantime this is it :) And to prove I mean it this is the first
version of NUTS for a long long time without a backdoor in it as I'm sure 101
hackers will test and find out to be true :)

Unfortunately I still haven't found out what the colour reset code for
SCO consoles and strict ansi terminals is so if you're using one of these 
things may look messy. No one mailed me the code and the SCO terminfo 
translation tools proved less than helpful so theres not much I can do. Sorry.

Now go and read the DOCS/compiling file for info on how to get started if 
you're new to NUTS and all the other files there will be usefull in time also.

Neil Robertson - November 1996

email: neil@@ogham.demon.co.uk
home page     : http://www.wso.co.uk/neil.html
NUTS home page: http://www.wso.co.uk/nuts.html

NB: If anyone is also interested in MUDs I've written a MUD system called 
    Ogham - ftp.ccs.neu.edu:/pub/mud/servers/misc/ogham/ogham262.tar.gz
    Its not as complex as perhaps LPmuds or Dikumuds are but if you know C and 
    want to set up a low to medium complexity mud then this is just what you 
    need :) 
    
@


1.10
log
@A few changes including the removal of information about manual AUTH
lookups as that was moved into a separate file.
@
text
@d1 1
a1 1
*** README for 3.3.2 ***
d19 10
a28 7
I've found out about a problem with the colour on a SCO console. For some 
reason the terminal reset code does not reset the colours so they stay 
effective until another colour is specified. No doubt there is a specific code 
to do a colour reset but at the moment I don't know what it is. If you 
are using SCO and have trouble you'll just have to make do with colour off or 
use an xterm under X windows. Sorry. If anyone does know the code could you
email it to me.
a31 2
The auth lookup stuff that was in the readme in the 3.3.1 distribution has been
moved to its own file in DOCS.
d40 1
a40 1
    Ogham - ftp.ccs.neu.edu:/pub/mud/servers/misc/ogham/ogham260.tar.gz
d43 1
a43 3
    need :) The final release of Ogham + mudlib (2.6.0) was released in early 
    June but there is now a patch release which will upgrade you to 2.6.1
    called ogham261_patch.tar.gz but I'm hoping to release 2.6.2 soon.
@


1.9
log
@Some new comments were added including information on the manual use of
the auth daemon.
@
text
@d1 1
a1 1
*** README ***
d13 13
a25 44
of it. If however theres a problem with my code please feel free to email
me about it.

This versions main change is that the local port number of the user connected 
is available using .site command, is stored in the syslog and follows the
SIGN ON: when seen by wizes and above. It appears after a colon following the 
address eg ogham.demon.co.uk:1234
The reason I have done this is so manual user identity lookups can be done on 
a site if you so desire (automatic lookups means lots of extra code) to 
supposedly verify a users real identity though bear in mind that fake auth 
daemons can be easily written (about 2 hours work I'd say for an experienced 
tcp/ip C programmer starting from scratch).
To do a manual lookup telnet to port 113 on the users site (if you get a 
connection refused message they don't have an auth daemon running) and enter 
the following:

<their local port number>,<talkers port number>

So for instance if they're logging in on the talkers main port on 7000 and
their local port is 1234 enter:

1234,7000

You should see something like the following:

Trying sad.hackers.org...
Connected to sad.hackers.org.
Escape character is '^]'.
1234,7000
1234 , 7000 : USERID : UNIX : weenie     <--- The reply
Connection closed by foreign host.

As you can see the final field is the user id but if you see this...

1234 , 7000 : ERROR : NO-USER

then something is wrong. Bear in mind that this will only work while the user
is logged onto the talker so if you wish to do it do it quick! Also YOU MUST 
TELNET FROM THE SAME MACHINE THAT THE TALKER IS RUNNING ON. There ends the 
lesson on manual auth lookups. If you're wondering whether I'll put automatic
lookups in future NUTS releases (assuming there'll be any) the answer is no
as the majority of sites do not have auth daemons in the first place eg a
windows PC is very unlikely to have one :), so the effort would not be worth
it , besides doing the lookup could hang the talker if there's net lag.
d28 3
a30 2
you're new to NUTS. 

d32 1
a32 1
Neil Robertson - October 1996
d44 1
a44 1
    called ogham261_patch.tar.gz.
@


1.8
log
@This file was updated to provide information on the state of NUTS since the
3.2.1 release. In particular it mentions that there have been a few bug fixes
since the previous release. Also, he has tried to start a newsgroup for NUTS.
@
text
@d5 52
a56 10
OK , so 3.2.1 was going to be the final version. So I lied (but not 
intentionally :) This version has a number of bug fixes as usual and some
new features. Can't think of much else to say about it really so I'll leave
it at that.

I've tried to create a newsgroup called alt.talkers.nuts but it doesnt
seem to be propagating very fast. Anyway , hopefully it'll arrive at
your site at some point :) Theres always alt.talkers in the meantime. 
I will crosspost anything I put on alt.talkers.nuts to alt.talkers for the
time being.
d62 1
a62 1
Neil Robertson - September 1996
@


1.7
log
@This file was updated to provide information on the state of NUTS since the
3.2.0 release.
@
text
@d5 10
a14 23
This is *it*, 3.2.1 is the final version of NUTS .. ever (probably :). Even if 
there turn out to be bugs in this version I still won't be releasing another, 
however I may keep an updated list of known bugs on the NUTS home page (see 
below). I've decided there probably won't be a version 4 as the way the 
internet is slowing down these days talkers will probably be so laggy as to be 
useless in a couple of years time (Call me a cynic , I don't care :) so there 
won't be any point :) 

I reckon I should have added a .revtell at some point but sod it,I couldn't be 
bothered. Also something that came to mind was .lock and .unlock commands 
which locked the session so that you could wander away from your keyboard for 
a while and not have to worry about some moron sitting next to you in the lab 
abusing your account. You would simply use .lock on its own to lock the session
but would have to do .unlock <your password> to unlock it. This is fairly easy 
to implement so I'll leave it up to you to sort it out :) Something else that
I thought of (if I ever do a version 4) is to have a user definable front end 
to the talker so you can control the way it looks to you and also have a simple
scripting language that would allow triggers , macros, automatic events when 
you log on/off etc and negate the need for flash clients such as TUsh.

If I get enough email persuading me to do a version 4 in a few years then I
may consider it , in the meantime the above is just a gleam in this busy
programmers eye :)
d20 1
a20 1
Neil Robertson - July 1996
d30 3
a32 1
    need :) The final release of Ogham (2.6.0) was released in early June.
@


1.6
log
@This file was updated to provide information on the state of NUTS since the
3.1.2 release.
@
text
@d5 7
a11 9
This is going to be the last major release of NUTS 3. There may well be further
patch releases if needs be (eg 3.2.1) but as far as features goes , this is
it. There will be no version 3.3 though maybe in a few years I may do a 
version 4 if I get bored. Certain things which I had suggested I might put
in this version are missing - saving statistics for instance - this is simply
because I couldn't be bothered to put them in. :) Other things either required
too much rehacking of the code (eg mail forwarding) or were simply too complex
for me to bother doing (eg user defined rooms) though of course there is 
nothing to stop any of you lot implementing them :)
d13 11
a23 1
Now go and read the DOCS/compiling file for info on how to get started.
d25 9
a34 1
Neil Robertson - June 96
d36 2
d39 6
a44 1

@


1.5
log
@This file was updated to provide information on the state of NUTS since the
3.1.1 release.
@
text
@d1 1
a1 2

*** NUTS 3.1.2 readme file ***
d5 9
a13 40
Yet more bugs have been nailed for this release however there are probably 
still some around , so because of this I've put an option in the config file 
called "crash_recovery". Read the doc for more information. Apparently this 
program dies horribly on IRIX 5.3 as soon as someone attempts to log in. I may
have solved it in this release but since I don't know what the problem was in 
the first place theres no way to tell.

Compiling...

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 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 nuts312.c" to compile though
for HP-UX you need to type "cc -Ae nuts312.c". 
Please note that you NEED the ANSI compiler for HP-UX, the bundled K&R one
is useless.

Running...

The talker comes with a config file ready made (datadir/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.
d15 1
a15 2
More detailed information is in the specific documentation in the DOCS
directory.
a16 1
Neil Robertson , April/May 1996
d18 2
a19 1
neil@@ogham.demon.co.uk
a20 1
PS: If you have any ideas for future releases mail me about them.
@


1.4
log
@This file was updated to provide information on the state of NUTS since the
3.1.0 release.
@
text
@d2 1
a2 1
*** NUTS 3.1.1 readme file ***
d4 1
a4 2
Ive moved this too the top since a number of people seemed to think that 
because I put it at the end last time I wasnt serious so...
d6 6
a11 19
------------------------------------------------------------------------------
Could you please leave the credits in the code (.help credits) and also
don't change the version so much that it doesn't say NUTS anymore when a user
does the .version command. I find it annoying that after I've spent
months of time working on this software someone comes along , changes a few 
commands then pretends its all their own work. If you have a problem
with any references to my name or NUTS being on your talker then don't use my
software, its that simple, go write your own from scratch. This software
is freeware , it is *NOT* public domain, I retain copyright, and since there is
code in here than I have used in a commercial system I have written I will
take legal action on anyone and their institution/employer who I find using it
to their own commercial advantage.
------------------------------------------------------------------------------

I've tried to track down bugs that have been causing intermittent crashes 
and I've found a few but no doubt there are still some there. Unfortunately 
a full time job, a life beyond my keyboard and intolerance to boredom prohibit
me spending all my waking hours trawling the code for them but if I do spot 
some more or someone tells me of some then expect version 3.1.2 to appear :)
d19 1
a19 1
hack it about a bit or more to a different system.
d24 2
a25 2
	Generally you'll just need to enter "cc nuts300.c" to compile though
for HP-UX you need to type "cc -Ae nuts300.c". 
d50 1
a50 1
Neil Robertson , March 1996
@


1.3
log
@This file was updated to provide information on the state of NUTS since the
3.0.0 release. In particular, it mentions the addition of 'cloning'.
@
text
@d2 1
a2 1
*** NUTS 3.1 readme file ***
d4 2
a5 2
This version has a major feature that the previous release did not which
is the cloning facility. See the documentation for more details.
d7 19
a25 4
Before I proceed a number of people have mentioned that the documentation
with NUTS isn't all that good. Well , you're right , its not, because I hate
writing it. Anyway , most of you will be smart enough to figure out anything
I havn't mentioned by yourselves. Now onwards with the waffle...
a62 12

And finally a request...

Could you please leave the credits in the code (.help credits) and also
don't change the version so much that it doesn't say NUTS anymore when a user
does the .version command. I find it annoying that after I've spent
months of time working on this software someone comes along , changes a few 
commands then pretends its all their own work. If you have a problem
with any references to my name or NUTS being on your talker then don't use my
software, its that simple, go write your own from scratch. This software
is freeware , it is *NOT* public domain, I retain copyright and will defend
it if needs be.
@


1.2
log
@This file was updated to provide information on the state of NUTS since the
3.0.0 alpha release.
@
text
@d2 1
a2 1
*** NUTS 3 readme file ***
d4 7
a10 18
Well , only 1 person bothered to test the alpha release for me and he
didnt have time to do much of that so if there are still bugs in this
final release blame yourselfs. I've got rid of all the bugs I can find but
the program still needs and effective soak test with many users. The user
data files are incompatible with the alpha release by the way. If you have
a problem with that, well its just tough titties.

From a initial glance this version of the talker looks pretty similar to all
the other versions. Up to a point this is correct, after all there are only
so many things you can do with a talker to make it look original and 
different, espcially a text based one. However, under the skin things are 100%
new. The entire code has been rewritten and a number of major new features 
have been added (one has also been removed - the atmospherics, no one liked
them or used them so I dumped them) including the biggest new feature of all
which is having networked talkers, ie you can log into one talker and wander
into another talker simply by typing "go <room name>". This will be explained
more clearly in the documentation in the DOCS directory so now I will turn
to the more prosaic field of compilation and how to get started...
d14 5
d34 5
a38 4
	To start the talker just type "a.out" 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.
d49 12
d62 5
@


1.1
log
@Initial revision
@
text
@d4 6
a9 4
This is an alpha release. As such this means the documentation may be a bit
ropey and the server itself may have problems and bugs. PLease mail me with
any problems be they functional or presentation wise and I'll try to put a
fix in the final release version.
d42 1
a42 1
syslog file. To log in you then just telnet to port 5000 and log in as "fred"
d54 1
a54 1
Neil Robertson , Feb 1996
@
