Running MudOS

Once you've successfully unpacked, configured, and installed MudOS (and you did read the installation document, right?) you're ready to try running it.

If you followed the installation directions carefully, you (or ./build.MudOS) should have specified an installation directory as part of the Makefile. Note that ./build.MudOS will do this for you, and that it defaults to ../bin. If for some reason the installation directory wasn't specified or couldn't be written to but the rest of the build process was successful, the driver file should be in the src directory. If necessary, copy it to wherever you plan to keep it.

Change to the directory where the driver file is located. Note the location of your configuration file, or copy it into the driver's directory.

Enter the command: 

    ./driver /path/config.mymud
where path is the absolute path to your configuration file (. if you copied the configuration file to the driver's directory) and "config.mymud" is replaced with the name of your configuration file. If you specified the path to your configuration file when you edited local_options, you can omit the name of the configuration file entirely.

If all is well and the gods are smiling upon you, the driver will start and you will see the startup messages. Once initialization has completed (usually a few seconds to a few minutes, depending on your mudlib and host) you can attempt to log into your mud using telnet.

The driver will remain running until you shut it down from within the mud (usually with a command like 'halt' or 'shutdown'), kill it externally using the kill command, or the system goes down. For a production mud, you will need to have some sort of script and procedure to keep the mud running despite system reboots. This may be part of your mudlib package.

If you have trouble at this point, see the crashed file.

Page design by Frank Jacquette & Tim Hollebeek
Copyright (C) 1998 Tim Hollebeek & Frank Jacquette
 		Back to MudOS