bh: server README.1st,1.21,1.22
cvs at intevation.de
cvs at intevation.de
Tue Jun 14 21:27:56 CEST 2005
Author: bh
Update of /kolabrepository/server
In directory doto:/tmp/cvs-serv9431
Modified Files:
README.1st
Log Message:
- Add some generic update instructions.
- move the reference to kolab.org to a better location. It somehow got
mixed up in the release specific notes.
Index: README.1st
===================================================================
RCS file: /kolabrepository/server/README.1st,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -d -r1.21 -r1.22
--- README.1st 7 Jun 2005 16:05:23 -0000 1.21
+++ README.1st 14 Jun 2005 19:27:53 -0000 1.22
@@ -1,5 +1,7 @@
-Kolab2 Important Information
-============================
+Kolab2 Server Important Information
+===================================
+
+For more information on Kolab, see http://www.kolab.org
WARNING: For rc2 we recomment disabling the "envelope header from" check in
/kolab/etc/kolab/templates/resmgr.conf.template
@@ -7,20 +9,10 @@
Otherwise emails originating from your server going through an external
mailinglist might not reach users inside of your domain because of Issue783.
-WARNING: There's an incompatible change between Beta 1 and Beta 2. See
-below for more information.
-
-WARNING: Check the permissions of your files in /kolab/etc/kolab/ after
-installing or upgrading. Especially kolab.conf and copies shall only be
-readable to the owner (usually "kolab").
-
-The installation and configuration script have been changed to make sure
-that the permissions are correct but there's a chance that the
-permissions can still go wrong, especially if you upgrade from pre Beta
-1 releases.
Quick install instructions
--------------------------
+
For a fresh install /kolab needs to be an empty directory with enough space.
You can use a symlink, but do _not_ use an NFS mounted drive.
Make sure that the following names are not in /etc/passwd or /etc/groups,
@@ -40,6 +32,35 @@
and follow the instructions.
+General update instructions
+---------------------------
+
+Usually an update of the Kolab 2 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
+instructions for all releases newer than the one you already have before
+you start the update.
+
+The installation of the new packages works just as for the initial
+installation. Download the files as described above and run
+
+# ./obmtool kolab
+
+obmtool will usually automatically determine which packages need to be
+built. Then regenerate the configuration with
+
+# /kolab/sbin/kolabconf
+
+
+You may want to check the permissions of your files in /kolab/etc/kolab/
+after installing or upgrading, as there have been problems with this in
+the past. Especially kolab.conf and copies shall only be readable to
+the owner (usually "kolab"). The installation and configuration scripts
+should make sure that the permissions are correct but there's a chance
+that the permissions can still go wrong, especially if you upgrade from
+pre Beta 1 releases.
+
+
Upgrading from earlier versions
-------------------------------
@@ -156,8 +177,6 @@
Distribution lists now have a mail attribute. Use an LDAP editor
to fill the mail attribute for all kolabGroupOfNames objects with
the email address of the distribution list.
-
-For more information on Kolab, see http://www.kolab.org
Upgrade from RC1
More information about the commits
mailing list