Congratulations, you now have TeenyMud 1.2, the most delicious and
machine-friendly program available.  Good luck with it!

Compiling
---------

	As distributed, this release should compile at most three binaries on
any normal BSD type of UNIX operating system. There are some #defines at the
beginning of includes/config.h that adjust the server to compile on different
operating systems. This particular release has been compiled under 4.3BSD and
AIX 3.1.
	Before continuing, edit includes/config.h NOW to personalize your
mud and choose which options you want to use.  If you change config.h after
compiling, you'll have to compile again.

	`make teeny' will compile the server
	`make teenydbm' will compile the database manager
	`make convert' will compile the database converter (See convert.doc)


Starting the server
-------------------

	See teeny.doc, then from csh type something like:
		teenymud -s -C 10 >& logfile &

	So then you'll have chunky.bits and chunky.index files, and you'll
have a mud.  From then on, from sh, you can run startserver, a simple
shell script which will start the mud.  Run it background.
		sh
		startserver &
		exit

	Of course there are other ways to make it run.  Main thing to
keep in mind is to get your flags right, and redirect error output to 
a file, and run it in background, and away you go.

Restarting from a crash
-----------------------

	Okay, suppose that the power goes out, your sysadmin hits you with
a kill, or Grod forbid, the program slams into a bug and crashes.  The index
and the bits file will be _out_of_sync_.  Therefore it is very important
to replace the chunky files with old ones before starting the mud again.

	cp old.bits chunky.bits; cp old.index chunky.index

	This will replace the spammed db with the last-saved db, which,
unless you change the parameter in config.h, updates every hour.  Also, it
is a good idea to save a copy of the db, either a bits & index pair or a
textdump, in a different directory, and update that every few days or weeks,
just in case someone like Dirque comes along and decides you need an extra
200,000 objects named 'SPAM' in your db.  (After that, you'll probably switch
to registration.)

Guest character
---------------

	There is nothing magic about a guest character in teenymud.  Just
create a character with the name guest and the password of guest, and there
you go.

Changes to this release
-----------------------

	If there's too many to count, how am I supposed to list them? Read
the code, that's what it's there for.


Help, News, Logs, the Universe, and Everything
----------------------------------------------

	If the appropiate options are set in config.h, TeenyMUD features a
simple help and news system. Basically, in addition to "text/help" and
"text/news", any files stored in the help and news subdirectories are
available to players, i.e., if there was a file in the help directory named
"@stats", it would be displayed if a player typed "help @stats", or even
if they typed "help @STATS". Files should have lowercase names. Hopefully
there will be some help files available with the next release. The news
directory works the same way as the help directory, see mud/help.c.

	Teeny doesn't normally want to send anything to stderr anymore,
and prefers to send logfile type things to various log files. See
includes/config.h.  Some error messages may get sent to stderr, however.

	Teeny tries to work as it's expected to, with some exceptions.
Here are the oddball commands that may come in handy, and their syntax:
	@find [<name>] [=<type>]
	@owned <player> [=<type>]
	@stats [<player>]
	@purge <player>
	@toad <player> [=<newowner>]
	@textdump [<filename>]
	@edit <object>/<string> = <old substring>,[<new substring>]

	Note that Teeny now sends \r\n newline termination, so VMS and
MSDOS users should be happy campers.  Well, they still use VMS and MSDOS, so
they can't *really* be happy campers, but you know what we mean.


Mailing List
------------

	The TeenyMUD mailing list is `teeny-list@fido.econ.arizona.edu'.
Send e-mail to `teeny-list-request@fido.econ.arizona.edu' if you'd like
to be put on this list. All sorts of ideas and stuff are discussed on the 
list, so if you're setting up this code, you should be on it.