Origin: lima_v1_fluffos.zip

Author: Yucong Sun

INSTALL

@@ -0,0 +1,76 @@
+If at any point you have problems with these directions, post the 
+exact problem and errors on http://lpmuds.net/forum
+
+How to install Lima:
+
+1) Compile the driver for your machine:
+	a) cd to the driver directory
+	b) Type: ./configure lima
+	c) When it is done running, type: make install
+	d) When this is finished, you should have a driver and an
+	   addr_server in ../bin
+
+2) You must edit the mudlib configuration file.
+	a) cd ../bin
+	b) edit the file config.lima
+	c) follow the directions in the file
+        d) at a minimum you MUST change the mud name, the bin directory, and the lib directory
+
+3) Start your address server if one isn't running already (type this while
+   you're in the "etc" directory):
+	./addr_server 9990 &
+
+   Change the port number above as needed, ensuring that the config.lima
+   file matches the command line used to start the address server.
+
+4) Start the driver with the command (type this while in the "etc"
+   directory):
+	./driver ./config.lima &
+
+   Your mud should now be starting up.  When it says:
+	Accepting connections on port NNNN.
+
+   Then your mud is up.
+
+5) Log in to your mud.  Make sure you're the first person to do so --
+   whoever is first will become an admin!  After that, new users will
+   just be guest wizards (by default).
+
+   Connect to the mud, type a name, password, etc.  Once you are logged
+   in, you should be a full admin.  To verify this, type:
+	checkpriv 1
+
+   It should come back with:
+	Verified.  You have privilege '1'
+
+   In order to access all the admin commands, you will need to type:
+	resetpath
+
+6) Creating new admins;
+
+   You can convert other wizards after they log in into admins by adding
+   them into the "admin" domain.  Use the "admtool" command for this.
+
+7) Mudlib configuration:
+
+   Change any options you feel appropriate in /include/config.h. 
+
+   When you're done with any configuration changes, then shut down the
+   mud with the shutdown command.  Restart it, as described above, to
+   make those changes happen.
+
+8) You're done! Share your experiences on the Lima area of http://lpmuds.net/forum
+
+9) If your machine has /bin/bash, you can modify LIMADIR in
+   /etc/backup and /etc/startmud, and follow the usage instructions in
+   those scripts, if you think you'll find them useful.
+
+10) Intermud channel rules - please comply with  the rules for the main
+   intermud channels, icode and igossip, which are at
+   http://lpmuds.net/intermud.html
+
+To join:
+chan imud_imud_gossip /on
+igossip foo
+chan imud_imud_code /on
+icode bar

INSTALL-windows.txt

@@ -0,0 +1,52 @@
+If at any point you have problems with these directions, post the 
+exact problem and errors on http://lpmuds.net/forum
+
+How to install Lima for windows:
+
+1) Uncompress this package and move/rename the folder so that the folders like bin and lib 
+   are in c:\lima
+
+2) Use wordpad to edit c:\lima\bin\config.lima.win32 and change the mudname
+
+3) Double-click on c:\lima\win32\mud.bat
+
+4) telnet to localhost 7878
+
+5) Log in to your mud.  Make sure you're the first person to do so --
+   whoever is first will become an admin!  After that, new users will
+   just be guest wizards (by default).
+
+   Connect to the mud, type a name, password, etc.  Once you are logged
+   in, you should be a full admin.  To verify this, type:
+	checkpriv 1
+
+   It should come back with:
+	Verified.  You have privilege '1'
+
+   In order to access all the admin commands, you will need to type:
+	resetpath
+
+6) Creating new admins;
+
+   You can convert other wizards after they log in into admins by adding
+   them into the "admin" domain.  Use the "admtool" command for this.
+
+7) Mudlib configuration:
+
+   Change any options you feel appropriate in /include/config.h. 
+
+   When you're done with any configuration changes, then shut down the
+   mud with the shutdown command.  Restart it, as described above, to
+   make those changes happen.
+
+8) You're done! Share your experiences on the Lima area of http://lpmuds.net/forum
+
+9) Intermud channel rules - please comply with  the rules for the main
+   intermud channels, icode and igossip, which are at
+   http://lpmuds.net/intermud.html
+
+To join:
+chan imud_imud_gossip /on
+igossip foo
+chan imud_imud_code /on
+icode bar

bin/backup

@@ -0,0 +1,58 @@
+#!/bin/bash
+#
+# standard backup script by Rust@TMI-2 (rust@virginia.edu) Jul 7, 1994
+# reworked for more flexibility by Deatblade@Quendor (gstein@svpal.org)
+#    on Mar 31, 1995
+# Rust added an exec to a new expect script that automatically ftp's
+# the backup to a remote host.
+# - Deathblade took it back out and installed another cron
+#   entry.  It made it a bit difficult to do a backup without
+#   a mirror being done. :-)
+# Jun 7, 1995: Deatbhlade altered for distinct daily backups with a running
+#   monthly longterm backup.
+#
+# If you add the following entry to your crontab:
+# 36 4 * * * ~/bin/backup  (assuming this is installed in ~/bin/backup)
+# then this script will back up your lib daily into different files.
+# The monthly will be hard link (therefore taking no extra disk space),
+# but the link is "broken" at the turn of the month; essentially, it
+# will drop off a copy each month.  This system provides for restoring
+# from up to a few days and for long term archival.
+#
+#
+# CONFIGURABLE STUFF
+#
+limadir=/home/David/lima-1.0b5
+backupdir=$limadir/backups
+targetdir=$limadir/lib
+COMPRESSCMD=gzip
+#
+# END
+#
+
+
+
+base=$(basename $targetdir)
+log=$backupdir/$base.log
+
+echo Backup begun: $(date) >> $log
+
+cd $targetdir/..
+
+if [ -f ./$base/core ]; then
+  mv ./$base/core ./core.$base.$(date +%y%m%d)
+fi
+
+tar -cf $backupdir/$base.tar ./$base
+$COMPRESSCMD $backupdir/$base.tar
+
+weekday=$(date +%w)
+month=$(date +%m)
+rm -f $backupdir/$base.$weekday.tar.gz
+rm -f $backupdir/$base.$month.tar.gz
+mv $backupdir/$base.tar.gz $backupdir/$base.day$weekday.tar.gz
+ln $backupdir/$base.day$weekday.tar.gz $backupdir/$base.$month.tar.gz
+
+echo "  Files: $base.day$weekday.tar.gz $base.$month.tar.gz" >> $log
+echo Backup finished: $(date) >> $log
+