[DGD] 1.2.41

[Felix A. Croes]

diff -c dgd/src/Changelog:1.279 dgd/src/Changelog:1.280
*** dgd/src/Changelog:1.279     Sun Mar 17 22:35:53 2002
--- dgd/src/Changelog   Fri Mar 22 00:09:51 2002
***************
*** 1504,1506 ****
--- 1504,1509 ----
     catches.
   - Fixed a bug in upgrading light-weight objects.
   - DGD can now listen on multiple ports (currently Unix and Windows only).
+  - Fixed a config file reading bug that could occur if the server was restarted.
+  - Add arrays of telnet ports and binary ports to status().
+  - Include the server name with the version number.

ftp://ftp.dworkin.nl/pub/dgd/experimental/1.2.40-1.2.41.gz


The driver name is now included in the version string, which may break
code that only expects a version number.

The kernel lib that comes with 1.2.41 has several changes that are not
backward compatible.  You must now specify a separate connection manager
for each port, instead of one for each connection type.  Furthermore,
the compile_string() and compile_lib_string() functions that are called
in the object manager have been merged into their compile() and
compile_lib() counterparts.

To upgrade with an existing statedump, proceed as follows:

 - adjust your object manager to the new interface, but do not recompile
   it yet;
 - temporarily add something similar to the following to the reboot()
   function in /usr/System/initd.c:

    "/kernel/sys/userd"->set_telnet_manager(0, find_object(TELNETD));
    "/kernel/sys/userd"->set_binary_manager(0, find_object(BINARYD));

   (possibly adding more lines for ports above 0);
 - recompile /kernel/sys/driver.c and the object manager in the same
   command line;
 - upgrade the rest of the system normally, including /usr/System/initd.c.

The important part is that the driver object and the object manager are
recompiled in the same thead, so that the interface change is made on
both sides at the same time.

If you are upgrading from before 1.2.40 to 1.2.41 or later, perform
these actions with the old version of the driver still running, and
then reboot; note that nobody will be able to login between the time
you upgrade the mudlib in the penultimate step, and the moment you
reboot with the new driver version.

Regards,
Dworkin
_________________________________________________________________
List config page:  http://list.imaginary.com/mailman/listinfo/dgd