thomas: server README.1st,1.60,1.61
cvs at kolab.org
cvs at kolab.org
Fri Oct 19 12:53:46 CEST 2007
Author: thomas
Update of /kolabrepository/server
In directory doto:/tmp/cvs-serv12034
Modified Files:
README.1st
Log Message:
Removed obsolete info. Describe install with horde/fbview by default.
Index: README.1st
===================================================================
RCS file: /kolabrepository/server/README.1st,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -d -r1.60 -r1.61
--- README.1st 19 Oct 2007 09:06:41 -0000 1.60
+++ README.1st 19 Oct 2007 10:53:44 -0000 1.61
@@ -8,11 +8,13 @@
http://kolab.org/mailman/listinfo/kolab-announce
to receive security advisories and release announcements.
+* This development snapshot is not recommended for use in production! *
+
Quick install instructions
--------------------------
-For a fresh install /kolab needs to be an empty directory with at least 1GB of
+For a fresh install /kolab needs to be an empty directory with at least 2GB of
free disk space. You can use a symlink, but do _not_ use an NFS mounted drive.
If the directory does not yet exist, it will automatically be created.
Make sure that the following names are not in /etc/passwd or /etc/groups,
@@ -21,7 +23,7 @@
Check http://www.openpkg.org/documentation/ for additional documentation
for the OpenPKG packaging system.
-To install the Kolab2 server, you need to download the files from the
+To install the Kolab server, you need to download the files from the
directory containing this file (1st.README) to some local directory.
You can check the integrity of the downloaded files with:
@@ -29,23 +31,24 @@
$ gpg --verify MD5SUMS
$ md5sum -c MD5SUMS
-Then as root, cd into that local directory and run
+Then as root, cd into that local (and writable) directory and run
-# ./install-kolab.sh 2>&1 | tee kolab-build.log
+# ./install-kolab.sh -H -F 2>&1 | tee kolab-install.log
to build and install packages in /kolab. The command output will
-be logged to kolab-build.log so that you have a reference in case
+be logged to install-kolab.log so that you have a reference in case
an errors occurs during installation.
-If you wish to include the Horde groupware client and/or the Free/Busy
-view tool in you installation, you need to append the flag(s) "-H"
-and/or "-F". The following installs the server including Horde and
-F/B-View:
+If you do not want to install the Horde groupware client and/or the
+free/busy view tool, you can drop the flag "-H" and/or "-F".
-# ./install-kolab.sh -H -F 2>&1 | tee kolab-build.log
+FIXME: document install from read-only location (e.g. cdrom)
-By default, the Kolab Server will now be started at boottime.
-After the build/install is complete, please run
+By default, the Kolab server will now be started at boottime, so you
+have to bootstrap the server configuration now to prevent unconfigured
+components from being started.
+
+Please run:
# /kolab/etc/kolab/kolab_bootstrap -b
@@ -55,26 +58,25 @@
General update instructions
---------------------------
-Usually an update of the Kolab 2 server works as described here. In
+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
instructions for all releases newer than the one you already have before
you start the update.
In any case you should completely read *all* relevant update
-instruction *before* starting the upgrade procedure. All ways make
+instruction *before* starting the upgrade procedure. Always make
sure you have a recent backup of your /kolab directory before you
attempt to upgrade Kolab.
The installation of the new packages works just as for the initial
installation. Download the files as described above and run
-# ./install-kolab.sh 2>&1 | tee kolab-update.log
-
-If you installed with Horde or F/B-View you need to run
-
# ./install-kolab.sh -H -F 2>&1 | tee 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 have made changes to configuration files or
an updated package includes configuration files which are usually
@@ -95,223 +97,21 @@
# /kolab/bin/openpkg rc all restart
-Upgrading from earlier versions
--------------------------------
-
-Direct upgrade from Kolab1 is not recommendable at this point. We
-suggest that you back up your IMAP store, install Kolab2 and manually
-recreate user accounts and then restore the IMAP data from the backup.
-
-After an upgrade, always run /kolab/sbin/kolabconf to make sure the
-configuration files are regenerated from your templates.
-
-
-Upgrade from Kolab server 2.0 to 2.1
-------------------------------------
-
-Upgrading from Kolab 2.0.x to 2.1 is described in detail in the file
-UPGRADING.20-21 in this directory.
-
-The latest version of the upgrading instruction can be found in the
-Kolab.org raw-howtos CVS:
-
-http://kolab.org/cgi-bin/viewcvs-kolab.cgi/*checkout*/doc/raw-howtos/kolab_2.0_to_2.1_upgrade_instructions.txt
-
-Please read carefully all the following update instructions in this
-file, while some of the information will be redundant there might
-be additional notes which are essential for an successful update.
-
-
-Upgrade from pre-2.1-snapshot-20051130
---------------------------------------
-
-This upgrade is somewhat tricky, because of a new db package and a new
-OpenLDAP version. To make sure that no data is lost, you are strongly
-advised to stop the server and make a backup before you start the
-update. Some files are removed during the upgrade described below.
-
-
-1. Before installing the new RPMs
-
-Before installing the new packages, copy the contents of the openldap
-database (use a different output filename if you want):
-
- /kolab/sbin/slapcat > ~/kolab-slapcat-data
-
-
-The db update also affects the imap server.
-
- cd /kolab/var/imapd/db
- /kolab/bin/db_recover
- rm /kolab/var/imapd/db/*
-
-
-2. After installing the new RPMs
-
-You need to make two small changes are required for the openldap
-configuration file /kolab/etc/openldap/slapd.conf:
-
- - comment out the line
-
- require none
-
- - Move the line with the suffix setting to just after the "database
- bdb" line.
-
-These changes have already been done in the new slapd.conf.template, so
-it can be used for guidance.
-
-
-Then restore the openldap data:
-
- rm /kolab/var/openldap/openldap-data/*
- /kolab/sbin/slapadd -l ~/kolab-slapcat-data
-
-
-The IMAP server should work without further changes.
-
-
-Upgrade from pre-2.1-snapshot-20051215
---------------------------------------
-
-Nothing special has to be done for this upgrade.
-
-
-Upgrade from 2.1-beta-1
------------------------
-
-1. imapd hashimapspool setting
-
-The default imapd configuration has been changed to enable the
-hashimapspool option. This means that in 2.1-beta-2 the directory
-layout of the imapd spool (/kolab/var/imapd/spool/) is different from
-the one in beta-1. When you upgrade from beta-1 it's best to keep using
-the old structure, so remove or comment out the corresponding line in
-/kolab/etc/kolab/templates/imapd.conf.template *before* running
-kolabconf.
-
-For new installations the new default setting is recommended because
-it's more efficient especially when you have many mailboxes.
-
-For some background information about this see the dicussion at
-https://intevation.de/roundup/kolab/issue1089
-
-
-2. distribution lists
-
-There was a bug in earlier versions regarding the distribution lists for
-administrative emails aliases like postmaster@<domain>. They were
-created without the domain part. This has been fixed so that they are
-created with the correct domains in their names, but admin distribution
-lists created by an earlier Kolab server version will not be updated
-automatically. The easiest way to do this is by deleting them all and
-then to create them again with the services page of the web-interface.
-
-For more details about the bug, see
-https://intevation.de/roundup/kolab/issue1100
-
-
-Upgrade from 2.1-beta-2
------------------------
-
-1. postfix: ownership of virtual and transport:
-
-The owner of two config files has to be root, otherwise postfix will
-change to an unprivileged user for creating the corresponding .db files,
-isn't able to write them after the upgrade and fails to create further
-database files which don't get generated from kolab templates.
-
-To correct the file owner, execute the following commands as root:
- cd /kolab/etc/postfix
- chown root transport virtual
- make
-
-See kolab/issue1433 for details about this topic.
-
-
-2. imapd: database format for annotations.db and mailboxes.db
-
-The default database format for /kolab/var/imapd/annotations.db and
-/kolab/var/imapd/mailboxes.db has changed from skiplist to berkeley db.
-
-If you want to keep the old format, comment out or remove the lines
-"annotation_db: berkeley" and "mboxlist_db: berkeley" in the file
-"/kolab/etc/kolab/templates/imapd.conf.template" and make sure the file
-"/kolab/etc/imapd/imapd.conf" reflects this, too, by either running
-/kolab/sbin/kolabconf or changing it manually there, too.
-
-To convert the databases to berkeley db format, execute as root:
-
- /kolab/bin/openpkg rc imapd stop
- su - kolab-r
- cd /kolab/var/imapd/
- mv annotations.db annotations.db-skiplist
- cvt_cyrusdb /kolab/var/imapd/annotations.db-skiplist skiplist \
- /kolab/var/imapd/annotations.db berkeley
- mv mailboxes.db mailboxes.db-skiplist
- cvt_cyrusdb /kolab/var/imapd/mailboxes.db-skiplist skiplist \
- /kolab/var/imapd/mailboxes.db berkeley
- exit
- /kolab/bin/openpkg rc imapd start
-
-See http://wiki.kolab.org/index.php/Kolab2_IMAPD_annotations.db_Problems
-for details about this topic.
-
-
-Upgrade from 2.1-beta-3
------------------------
-
-1. Symlink from /kolab/kolab to /kolab no longer needed:
-
-Due to kolab/issue1490 a symbolic link was needed to fix a packaging
-problem which otherwise disturbed free/busy cache generation.
-It is no longer needed and may optionally be removed:
-
- rm /kolab/kolab
-
-
-2. imapd: emails with identical message-id header:
-
-In all previous releases the imap server discarded emails with identical
-message-ids received within three days. This caused multiple problems
-mentioned in kolab/issue1532.
-
-This change may cause duplicate messages in mailboxes due to cross postings,
-distribution lists or possible bugs in imap clients. If you want to revert
-to the old behaviour, please comment out or remove the line
-"duplicatesuppression: 0" in /kolab/etc/kolab/templates/imapd.conf.template
-or set the value to 1.
-
-
-Upgrade from 2.1-beta-4
------------------------
-
-Nothing special has to be done for this upgrade.
-
-
-Upgrade from 2.1-rc-1
----------------------
-
-The database backend for the free/busy cache was changed to solve licensing
-issues between php4+ and gdbm. See kolab/issue1607 for details.
-
-Follow the steps to regenerate the free/busy cache shown in the section
-"Final Steps" in the file UPGRADING.20-21
-
-
-Upgrade from 2.1-rc-2
----------------------
+Upgrade from 2.2-beta1 to 2.2-beta2
+-----------------------------------
-Nothing special has to be done for this upgrade.
+FIXME
-Upgrade from 2.1.0
-------------------
+Upgrade from Kolab server 2.1 or before
+---------------------------------------
-The free/busy cache should be regenerated if you need the 'location' entry
-in extended free/busy lists.
-FIXME: describe generatefb.php
+Instructions for upgrading from Kolab server 2.0 or 2.1 will be added
+in a future version of this document.
+Direct upgrade from Kolab1 is not supported. We suggest that you back up
+your IMAP store, install Kolab2 and manually recreate user accounts and
+then restore the IMAP data from the backup.
Known problems and workarounds
More information about the commits
mailing list