Updated: Thu Jun 06 1998 - MudOSa4DGD-1.1 | DriverLib for DGD-1.1xx
======================================================================
In order to make use of this archive you must be sure you have the
correct version of DGD (Dworkins Generic Driver), and that it will
compile under your system. This file will with a few words explain
how to use this archive to support your own mudlib under DGD.
First a brief explanation of the main directories:
/bin/ - binaries, scripts and config files
/data/ - default dumpstate directory (see: /bin/dgd.cf)
/doc/ - documentation
/mudlib/ - current mudlib
/mudlib/dgd/ - base for DriverLib w/custom objects
/mudlib/dgd/lib/ - DriverLib source
/tmp/ - default swap directory (see: /bin/dgd.cf)
Firstly we want to test if the bare-bone mudlib and DGD binary is working:
1) Configure 'dgd.cf' and replace the 'driver' binary in 'bin/' with
the compiled binary of the driver.
2) Test it by running 'bin/D' or 'bin/DD'
(startup or restore from dumpstate)
3) Logon by telnet to the host and port described in 'dgd.cf'
If everything was found to work okay, and you wish to implement a mudlib
of your own using the features of this package:
1) Put the mudlib source under 'mudlib/', leaving 'mudlib/dgd/' alone.
'mudlib/std' and 'mudlib/log' may be completely removed, as long
things defined there is redefined somewhere else, or dependencies
updated to the new form.
2) Modify 'mudlib/dgd/master.c', 'mudlib/dgd/simul_efun.c' and put
additional sfuns needed in 'mudlib/dgd/sfun/'
3) Modify 'mudlib/dgd/config.h' and 'bin/dgd.cf' to suit your needs.
4) Make a prayer.
5) Execute 'bin/D' or 'bin/DD'
6) Iterate through steps 1-5 until the driver comes up, you manage to
login and everything is found to work okay.
The steps in this document requires a bit of ground knowledge about DGD
and MudOS, and the programming skills to suit a new mudlib to the
conditions offered by this package.
Frank Schmidt (Simone@VikingMUD)
EMAIL: franks@idb.hist.no