You have successfully unpacked the MUDLINK version 2.6-Beta release.  PLEASE
go read the src/copyright.c file.  If you disagree with any portion of it,
delete this source code and go on with your life.

Put simply,  MUDLINK allows you to exchange remote pages and remote WHO lists 
between 2 or more MUDS.  It also allows you to check the spelling of words, 
look up words in a dictionary, thesaurus, familiar quotes, and CIA world fact 
book.  It provides for 2 (or more) way Conference rooms, including a rlook 
command.  MUDLINKS can be used to contact mjr style RWHO servers without 
causing the local MUD to freeze, and to obtain general information about remote
linked MUDs.  MUDLINK also provides for an admin defined @cron command.
The installation gives you 9 new commands.

Rpeers     Lists out known MUDs in the peers database.
Rpage      Sends a remote page to Player @ MUD.
Rwho       Get a WHO list for a remote MUD.
Rversion   Get MUDLINK's current version number.
Rlook      Look into a Conference room and/or its contents. (local command)
Rinfo      Get information about a remote MUD.
@spell     Check spelling for a word.
@dict      Look up a word in the dictionary, thesaurus, or CIA fact book.
@geo       Look up a city in the geography server run at umich.
@rwho      Contact a MJR style RWHO server and return the output.
Plus a admin defined @cron command that MUDLINK will execute every few minutes.

MUDLINK runs mostly independent of the local MUD server and therefore if 
it crashes or a network connection hangs it won't affect your MUD server.   
MUDLINK uses reliable TCP connections.  This means if the connection can be 
made, the information will eventually be transferred.  MUDLINK is 
multiplexing, thus it can exchange information with multiple MUDS very 
rapidly.  This software is capable of receiving and establishing connections 
but only with other MUDLINKs.  (With the exception of your local MUD)

MUDLINK interfaces with your MUD through a player.  Although many people may
say that this is a kludge, it isn't.  Today there are many different types of
MUDS.  Attempting to port source code to all of these is time consuming and
not a very efficient way of doing things.  However all MUDS have players and
most MUDS have some type of programming capabilities.  This gives us the
advantage of making MUDLINK more or less independent of the MUD type.  I
say "more or less independent" because it IS written for TinyMUD type servers.
I HAVE added support for  LP and Diku  MUDs at the C source code level.  Anyone
who is VERY familiar with these type servers and wants to help finish the port
should contact me at  howard@pa.itd.com

MUDLINK typically consumes not more then 400 of RAM with 100 database 
entries and 20 active connections.  The source is written in ANSI C and you 
need an ANSI compiler.  If you have gcc I'd suggest using it.  The limit on 
connections is set by the system OS.  Under SunOS and other machines that 
support the "unlimit" command you can gain up to 252 active connections at any 
given time.  All connections with MUDLINKs are password protected.  This means 
you MUST establish a mutual password with another MUDLINK before any 
information can be exchanged.

Now that you have an idea as to what MUDLINK is, go to the the install 
directory and read the INSTALLATION file.  Also you may wish to see the
how.it.works file.
