Updated for 1.8.0.

INSTALL

 # INSTALL -- installation instructions for the LysKOM server
 #
-# $Id: INSTALL,v 1.21 1995/01/08 11:26:15 ceder Exp $
+# $Id: INSTALL,v 1.22 1995/11/08 21:19:27 ceder Exp $
 # Copyright (C) 1991, 1992, 1993, 1994, 1995  Lysator Academic Computer Association.
 #
 # This file is part of the LysKOM server.
@@ -26,6 +26,11 @@
 
 This file describes how to build and install a LysKOM server.
 
+WARNING: This release of lyskomd may be unstable.  It has not been
+tested as much as previous versions.  You have been warned.  You are
+strongly encouraged to backup your database before you start lyskomd
+1.8.0 for the first time.
+
 Table of Contents:
 ------------------
 
@@ -53,6 +58,7 @@ A recent release (not necessarily the current release) of lyskomd have
 been tested on all of the following environments:
 
 	PC, Linux 1.1.75, gcc 2.6.3
+	PC, Linux 1.3.30, gcc 2.7.0
 	?, Ultrix 4.0, cc
 	HP 9000/340, HP-UX 8.0, gcc 2.4.5
 	Sequent Balance 8000, Dynix 3.0.14, gcc 2.4.5
@@ -80,9 +86,10 @@ make does not support it.
 
    2. From the top directory of the server sources, run configure:
 
-	$ ./configure --prefix=/usr/local/lyskom
+	$ ./configure --prefix=/usr/local/lyskom --with-gnu-malloc
 
-      The prefix defaults to /usr/lyskom.
+      The prefix defaults to /usr/lyskom.  By default, the systems
+      own malloc is used.
 
    2b. Edit src/server/tmp-limits.h
 
@@ -155,13 +162,13 @@ other file).  This section also describes everything you can change to
 get different behavior.
 
    1. Generate the configure script from configure.in.  This requires
-      GNU autoconf version 2 or later (we have been using version 2.1).
+      GNU autoconf version 2 or later (we have been using version 2.4).
 
 	$ autoconf
 
    2. Generate Makefile.in from Makefile.src.  There is
       (almost) one Makefile.src per directory.  As of this writing,
-      there are 16 of them.
+      there are 19 of them.
 
 	$ ./mkmi
 
@@ -169,8 +176,8 @@ get different behavior.
       The file scripts/mkmi.m4 contains m4 macro definitions which are
       used. If you want to change how the Makefiles work, it is
       probably there you have to do the change.  The Makefile.in files
-      which are distributed with lyskomd 1.6 were generated using GNU
-      m4 version 1.1.
+      which are distributed with lyskomd 1.8.0 were generated using GNU
+      m4 version 1.3.
 
    3. Run configure, to generate Makefile from Makefile.in.  You do
       not have to compile in the source directory.  This can be useful
@@ -181,7 +188,7 @@ get different behavior.
 
 	$ mkdir compilation-dir
 	$ cd compilation-dir
-	$ ../lyskom-1.6/configure
+	$ ../lyskom-1.8.0/configure
 
       The configure script understands (at least) these options:
 
@@ -189,6 +196,11 @@ get different behavior.
 		      	Note that this path will be compiled into the
       			programs, so try to get it right.
 
+	--help		List everything it understands.
+
+	--with-gnu-malloc  Use GNU malloc instead of the one supplied
+			by the system.
+
       The configure script also adheres to some environment variables,
       among them are:
 

NEWS

-NOT RELEASED YET
-Changes in lyskomd 1.8.0 (Release date 1995-11-??)
+Changes in lyskomd 1.8.0 (Release date 1995-11-08)
 --------------------------------------------------
 
-* WARNING: This release of lyskomd contains an incompatible change in
-  the database format.  Once lyskomd 1.8.0 saves the database you
-  cannot revert to older versions of 1.7.1.  This is because a
-  Conf-type now is 8 bits long.  The protocol is, of course, backwards
-  compatible, so you do not need to upgrade the clients to be able to
-  run lyskomd 1.8.0.  Just make sure you save a copy of your database.
-
 * If configured with --with-gnu-malloc lyskomd will use the GNU malloc
   package instead of the system-supplied malloc.  GNU malloc is
   included in the distribution.
@@ -17,7 +9,9 @@ Changes in lyskomd 1.8.0 (Release date 1995-11-??)
   most once per minute.
 
 * Lyskomd 1.8.0 implements protocol A level 8.  See doc/prot-A.txt for
-  information about the new features it contains.
+  information about the new features it contains.  The database
+  currently still only stores four bits of the conf_type, however, so
+  it is useless to use the new anarchy bit untill the next release.
 
 * You can now specify where lyskomd should dump core (if that should
   ever happen) using the "Core directory" parameter.