thomas: server README.1st,1.108,1.109

[cvs at kolab.org]

Author: thomas

Update of /kolabrepository/server
In directory doto:/tmp/cvs-serv15457

Modified Files:
	README.1st 
Log Message:
README: some clarifications and fixed typos


Index: README.1st
===================================================================
RCS file: /kolabrepository/server/README.1st,v
retrieving revision 1.108
retrieving revision 1.109
diff -u -d -r1.108 -r1.109
--- README.1st	5 Mar 2009 14:27:47 -0000	1.108
+++ README.1st	5 Mar 2009 14:46:04 -0000	1.109
@@ -13,10 +13,11 @@
 Quick install instructions
 --------------------------
 
-Kolab server with Horde needs about 1GB of disk space for the initial
-install. By default the directory /kolab will be used, which should be
-an empty directory or a symbolic link to an empty directory. If this
-directory does not yet exist, it will be automatically created.
+Kolab server and the Kolab web client (based on Horde) will use about 1GB
+of disk space for the initial install. By default the directory /kolab
+will be used, which should be an empty directory or a symbolic link to an
+empty directory. If this directory does not yet exist, it will be
+automatically created.
 
 For production use it is recommended to create a separate partition for
 /kolab (2GB to have some spare) and partitions for /kolab/var (at least
@@ -43,23 +44,23 @@
 
 # sh install-kolab.sh 2>&1 | tee /root/kolab-install.log
 
-to build and install packages in /kolab. The command output will
-be logged to install-kolab.log so that you have a reference in case
-an errors occurs during installation.
+to build and install packages in /kolab. The command output will be logged
+to install-kolab.log so that you have a reference in case an error occurs
+during installation.
 
 The install script needs to store some files and creates a subdirectory
 below /tmp (or $TMPDIR if set) for this purpose.
 
-Horde might create much load on your server if there are many concurrent
-users, so you can choose to not install it by adding the option
-"-x kolab-webclient" to the call to install-kolab.sh.
-Installing Horde on a separate host is possible, but not discussed here.
+The web client might create much load on your server if there are many
+concurrent users, so you can choose to not install it by adding the option
+"-x kolab-webclient" to the call to install-kolab.sh.  Installing the web
+client on a separate host is possible, but not discussed here.
 
 If you do not want to install the free/busy view tool, add the option
 "-x kolab-fbview".
 
-The binary packages distributed via kolab.org are compiled with Horde
-and the free/busy view tool. Currently you need to compile from the
+The binary packages distributed via kolab.org are compiled with the web
+client and the free/busy view tool. Currently you need to compile from the
 source packages to install without these features, see kolab/issue2440
 for details.
 
@@ -80,25 +81,25 @@
 General update instructions
 ---------------------------
 
-Usually an update of the Kolab server works as described here.  In
-some cases you will need to deviate from these instructions a bit.  All
-such cases are documented below, so read the release specific update
+Generally an update of the Kolab server works as described in this
+section, but often you will need to deviate from these instructions as
+described in the sections below.  Please read the release specific update
 instructions for all releases newer than the one you already have before
-you start the update.
+you start the update, e.g. for upgrading from 2.2.0 to 2.2.1-rc1 you have
+to follow the instructions for upgrading from 2.2.0 to 2.2.1-beta1, too.
 
-In any case you should completely read *all* relevant update
-instruction *before* starting the upgrade procedure.  Always make
-sure you have a recent backup of your /kolab directory before you
-attempt to upgrade Kolab.
+In any case you should completely read *all* relevant update instructions
+*before* starting the upgrade procedure.  Always make sure you have a
+recent backup of your /kolab directory before you attempt the upgrade.
 
 The installation of the new packages works just as for the initial
 installation.  Download the files as described above and run
 
 # sh install-kolab.sh 2>&1 | tee /root/kolab-update.log
 
-If you installed without Horde or F/B-View you need to drop the
-corresponding flags again.  install-kolab.sh will usually automatically
-determine which packages need to be built.
+If you installed without kolab-webclient or kolab-fbview you need to add
+the corresponding -x options again.  install-kolab.sh will usually
+automatically determine which packages need to be built.
 
 If you have made changes to configuration files or an updated package
 includes configuration files which are usually regenerated from files