[Kolab-devel] server/doc QIM,1.16,1.17 by martin at doto.intevation.de
root at intevation.de
root at intevation.de
Tue Jul 15 19:46:08 CEST 2003
Update of /kolabrepository/server/doc
In directory doto:/tmp/cvs-serv16921
Modified Files:
QIM
Log Message:
New versions. Corrected stuff as hinted by Ingo. Included instructions how to
install the Binaries on Debian 3.0
Index: QIM
===================================================================
RCS file: /kolabrepository/server/doc/QIM,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- QIM 10 Jun 2003 14:35:51 -0000 1.16
+++ QIM 15 Jul 2003 17:46:05 -0000 1.17
@@ -1,5 +1,5 @@
-Quick Install Manual - Kolab 1.0
+Quick Install Manual - Kolab 1.0 - Release Version (Gold)
Hi,
@@ -7,42 +7,23 @@
Please have a look at the documentation available from www.kroupware.org.
Please report Problems with the QIM or the software to kroupware at kde.org so that we can
-improve kolab permanently.
-
-Note that everything is also available via anonymous cvs from:
-
- CVSROOT=:pserver:anonymous at intevation.de:/home/kroupware/jail/kolabrepository
-
-You can check everything out to /kolab/RPM/SRC nicely (after setting the CVSROOT) with:
- cd /kolab/RPM/SRC
- cvs co -d apache server/apache
- cvs co -d imapd server/imapd
- cvs co -d kolab server/kolab
- cvs co -d monit server/monit
- cvs co -d openldap server/openldap
- cvs co -d postfix server/postfix
- cvs co -d proftpd server/proftpd
- cvs co -d sasl server/sasl
- cvs co -d doc server/doc
-
-For the Kolab 1.0 branch please use -r KOLAB_1_0 when checking out.
-
-If you update from an earlier beta version please see the section
-"recommended update procedure" further down!
+improve Kolab and its documentation permanently.
Upgrading from an alpha release we do not encourage, as the LDAP
layout has changed greatly. You may however want to manually merge
-old ldif data into the new tree, after the kolab installation.
+old ldif data into the new tree, after the Kolab installation.
=========================================================
Important!
We do currently depend on the latest unstable OpenPKG Current - As soon as
-available we will port to the soon expected OpenPKG 1.3
+available we will port to the soon expected OpenPKG 1.3. Actually OpenPKG is
+already very reliable so that this circumstance should not really matter to
+Kolab users currently.
We highly recommend to use the following environment variables in order
to be safe from some potential surprises.
-We have reports about Redhat Linux having problems with kolab otherwise.
+We have reports about Redhat Linux having problems with Kolab otherwise.
LC_ALL=C
LC_MESSAGES=C
@@ -52,69 +33,71 @@
=========================================================
-Preparation (with Source RPM's from our download URL)
+====== Installation from Source =========================
-1. Download everything from ftp://ftp.kde.org/pub/kde/unstable/server/kolab/kolab-1.0
+We recommend to install the Kolab Server from source though at the end of this
+QIM we provide instructions how to install from binaries on Debian 3.0 (woody).
-2. execute bootstrap compile shell script openpkg-20030516-20030516.src.sh
+Preparation of OpenPKG environment (see also http://www.openpkg.de)
+
+1. Download everything from http://www.erfrakon.de/projects/kolab/download/
+
+2. execute bootstrap compile shell script
+ http://www.erfrakon.de/projects/kolab/download/kolab-1.0/src/openpkg-20030606-20030606.src.sh
+
+ sh ./openpkg-20030606-20030606.src.sh --prefix=/kolab --user=kolab \
+ --group=kolab 2>&1 | tee kolab.log
+
+Please examine the log file kolab.log carefully for errors.
3. execute the resulting bootstrap install shell script (like
-openpkg-20030516-20030516.ix86-linux2.4-kol.sh)
+ sh -x ./openpkg-20030606-20030606.ix86-linux2.4-kol.sh)
-4. Add the following script to your startup files e.g. in /etc/init.d
+Please note the the binary shell script will have a slightly different name on
+non IA32-Linux systems.
+
+Now you succeeded in bootstrapping the kolab environment.
+You will have a new user kolab in your /etc/passwd.
+
+4. Add the following script to your startup files e.g. in /etc/init.d/kolab
#!/bin/sh
#
# kolab -- startup/shutdown transfer script for /kolab OpenPKG hierarchy
#
-[ ! -f /kolab/etc/rc.d/rc.monit ] && exit 0
+[ ! -f /kolab/etc/rc.d/rc.kolab ] && exit 0
case $1 in
start ) exec /kolab/etc/rc.d/rc.kolab start ;;
- stop ) exec /kolab/etc/rc.d/rc.kolab stop ;;
+ stop ) exec /kolab/etc/rc.d/rc.kolab stop ;;
esac
-=========================================================
-Quick Install Kolab Server 1.0
-
-Software was tested on Debian 3.0 stable.
-
-Note: you may use the provided buildkolab.sh script in order to make the build
-process easier and use the kolab anonymous cvs.
-
-1. download everything from
-ftp://master.kde.org/pub/kde/unstable/server/kolab
-
-2. as normal user execute
-sh ./openpkg-*.src.sh --prefix=/kolab --user=kolab --group=kolab 2>&1 | tee kolab.log
-
-Please examine the log file kolab.log carefully for errors.
-
-3. Install the resulting binary as root via
-sh ./openpkg-*-linux2.4-kol.sh
-
-Please note the the binary shell script will have a slightly different name on
-non IA32-Linux systems.
-
-Now you succeeded in bootstrapping the kolab environment.
-You will have a new user kolab in your /etc/passwd.
+5. Become the kolab user
+
+ su - kolab
-4. su - kolab
The kolab environment is selfcontained in /kolab. It has its own rpm database
etc. It explicitly will not interfere with your operating systems package
-database!
+database! Please make sure that whenever dealing with the Kolab server
+installation that you are using indeed /kolab/bin/rpm and _not_ the package
+manager of the hosting operating system. This can be easily accomplished by
+entering:
-5. As user kolab install source packages
+ export PATH=/kolab/bin:/kolab/sbin:$PATH
+
+5. As user kolab install the source packages
rpm -ihv *.src.rpm
6. compile and install the packages as user root according to the following pattern:
-cd /kolab/RPM/SRC/make
-rpm -bb make.spec
-(becoming root is required because we install daemon services. Please take care to use the correct path to rpm)
-/kolab/bin/rpm -Uhv /kolab/RPM/PKG/make-3.80-1.2.0.ix86-linux2.4-kol.rpm
+cd /kolab/RPM/SRC/PACKAGE
+rpm -bb PACKAGE.spec
+(becoming root for installing the rpms is required because we install daemon services.
+su # (become root)
+/kolab/bin/rpm -Uhv /kolab/RPM/PKG/PACKAGE-nnn-nnn.ix86-linux2.4-kol.rpm
-The compilation and installation of the other rpms is analogous to the make.rpm
+The compilation and installation of the following rpms is analogous.
+make
patch
binutils
gcc
@@ -146,9 +129,13 @@
db
mm
-and then compile and install (as root!) the kolab packages:
+and then compile (as user kolab) and install (as user root!) the kolab specific
+packages. For this you need to change directory to /kolab/RPM/SRC/PACKAGE and
+then create the binary package from there. Please take care to use the correct
+define statement. The later is mandatory for a functional Kolab server.
-(Please make sure that you use the correct OpenPKG rpm executable!)
+(Please make sure that you use the correct OpenPKG rpm executable when building
+the packages and installing!)
rpm -ba openldap.spec --define 'with_sasl no'
rpm -Uhv /kolab/RPM/PKG/openldap*kol.rpm
@@ -169,6 +156,9 @@
--define 'with_mod_auth_ldap yes' --define 'with_mod_php_openldap yes'
--define 'with_mod_php_imap yes' --define 'with_mod_php yes' \
--define 'with_mod_php_gettext yes'
+# if you encounter a missing ndbm.h when building apache please copy the
+# required header file manually
+# cp /kolab/RPM/SRC/gdbm/gdbm-1.8.3/ndbm.h /kolab/include/
rpm -Uhv /kolab/RPM/PKG/apache*kol.rpm
rpm -ba proftpd.spec --define 'with_ldap yes'
@@ -179,10 +169,10 @@
Please follow the instructions in the output when installing the kolab rpm
-caredfully.
+carefully.
-As root you may now start the kolab server via
+As root you may now start the kolab server manually via
/kolab/etc/rc.d/rc.kolab start
@@ -192,60 +182,118 @@
https://kolabserver.yourdomain.com/admin
-Note 2: Recommended Update Procedure from an older kolab installation
+Note 2: Note that kolab startup takes its time. Just give it some seconds and watch the
+syslog in the meantime. It should all come up nicely.
-If you update from an earlier beta version it is important
-that you backup your configuration first.
+On Linux the output of "netstat -ntplou" gives you an idea which services got
+activated.
-1. stop all kolab processes
- /kolab/bin/monit stop
- /kolab/etc/rc.d/rc.monit stop
- (make sure no kolab process is left)
+Note 3: For your convinience we also uploaded Debian 3.0 packages of the kolab
+server. Though compiling your own kolab server using this QIM should not be too
+difficult.
-2. make a copy of
- /kolab/etc/openldap/slapd.conf
- /kolab/etc/kolab/kolab.conf
-
- and backup your ldap database:
- slapcat > <filename of backup copy>
+====== Installation from Binaries =========================
-3. make the desired updates
+Currently we only provide binaries for Debian 3.0 (woody) other distributions
+and operating systems will follow.
-3a. due to community feedback the ldap layout has changed slightly:
- manually edit the slapcat output
- object: k=kolab,dc=...,dc=...
+We highly recommend to use the following environment variables in order
+to be safe from some potential surprises.
+We have reports about Redhat Linux having problems with Kolab otherwise.
- field "proftpd-userpassword" can be deleted
+ LC_ALL=C
+ LC_MESSAGES=C
+ LANG=C
+ SUPPORTED=C
+ export LC_ALL LC_MESSAGES LANG SUPPORTED
- fields to add:
- "uid: freebusy"
- "userPassword: <choice>"
+Installation of OpenPKG environment (see also http://www.openpkg.de for details)
-4. restore the old files
- /kolab/etc/openldap/slapd.conf
- /kolab/etc/kolab/kolab.conf
+1. Download everything from
+ http://www.erfrakon.de/projects/kolab/download/kolab-1.0/bin/Debian-3.0/
-5. rm /kolab/var/openldap/openldap-data/*
- slapadd -l <filename of backup copy>
+2. Install the bootstrap install shell script
+ sh -x ./openpkg-20030606-20030606.ix86-linux2.4-kol.sh
-5. start the ldap server
- /kolab/etc/rc.d/rc.openldap start
-6. re-create kolab config
- /kolab/etc/kolab/kolab -o -v
- (that means: -o "once" -v "verbose")
+Now you already succeeded in bootstrapping the kolab environment.
+You will have a new user kolab in your /etc/passwd.
-7. stop openldap
- /kolab/etc/rc.d/rc.openldap stop
+3. Add the following script to your startup files e.g. in /etc/init.d/kolab
-you should be done here and can regularly start kolab
-with /kolab/etc/rc.d/rc.kolab start
+#!/bin/sh
+#
+# kolab -- startup/shutdown transfer script for /kolab OpenPKG hierarchy
+#
+[ ! -f /kolab/etc/rc.d/rc.kolab ] && exit 0
+case $1 in
+ start ) exec /kolab/etc/rc.d/rc.kolab start ;;
+ stop ) exec /kolab/etc/rc.d/rc.kolab stop ;;
+esac
-Note 3: Note that kolab startup takes its time. Just give it some seconds and watch the
+The kolab environment is selfcontained in /kolab. It has its own rpm database
+etc. It explicitly will not interfere with your operating systems package
+database! Please make sure that whenever dealing with the Kolab server
+installation that you are using indeed /kolab/bin/rpm and _not_ the package
+manager of the hosting operating system. This can be easily accomplished by
+entering:
+
+ export PATH=/kolab/bin:/kolab/sbin:$PATH
+
+/kolab/bin/rpm -Uhv make-3.80-20030109.ix86-linux2.4-kol.rpm
+/kolab/bin/rpm -Uhv patch-2.5.9-20030520.ix86-linux2.4-kol.rpm
+/kolab/bin/rpm -Uhv binutils-2.14-20030613.ix86-linux2.4-kol.rpm
+/kolab/bin/rpm -Uhv gcc-3.3-20030614.ix86-linux2.4-kol.rpm
+/kolab/bin/rpm -Uhv procmail-3.22-20030330.ix86-linux2.4-kol.rpm
+/kolab/bin/rpm -Uhv zlib-1.1.4-20030227.ix86-linux2.4-kol.rpm
+/kolab/bin/rpm -Uhv expat-1.95.6-20030130.ix86-linux2.4-kol.rpm
+/kolab/bin/rpm -Uhv readline-4.3-20020718.ix86-linux2.4-kol.rpm
+/kolab/bin/rpm -Uhv perl*.ix86-linux2.4-kol.rpm
+/kolab/bin/rpm -Uhv openssl-0.9.7b-20030530.ix86-linux2.4-kol.rpm
+/kolab/bin/rpm -Uhv m4-1.4o-20020206.ix86-linux2.4-kol.rpm
+/kolab/bin/rpm -Uhv bison-1.35-20030604.ix86-linux2.4-kol.rpm
+/kolab/bin/rpm -Uhv flex-2.5.4a-20030402.ix86-linux2.4-kol.rpm
+/kolab/bin/rpm -Uhv pcre-4.3-20030530.ix86-linux2.4-kol.rpm
+/kolab/bin/rpm -Uhv fsl-1.1.0-20030522.ix86-linux2.4-kol.rpm
+/kolab/bin/rpm -Uhv gdbm-1.8.3-20030213.ix86-linux2.4-kol.rpm
+/kolab/bin/rpm -Uhv db-4.1.25.1-20030605.ix86-linux2.4-kol.rpm
+/kolab/bin/rpm -Uhv mm-1.3.0-20030307.ix86-linux2.4-kol.rpm'bison
+
+rpm -Uhv /kolab/RPM/PKG/openldap*kol.rpm
+rpm -Uhv /kolab/RPM/PKG/sasl*kol.rpm
+rpm -Uhv /kolab/RPM/PKG/postfix*kol.rpm
+rpm -Uhv /kolab/RPM/PKG/imapd*kol.rpm
+rpm -Uhv /kolab/RPM/PKG/apache*kol.rpm
+rpm -Uhv /kolab/RPM/PKG/proftpd*kol.rpm
+rpm -Uhv /kolab/RPM/PKG/kolab*kol.rpm
+
+
+Please follow the instructions in the output when installing the kolab rpm
+carefully.
+
+
+As root you may now start the kolab server manually via
+
+ /kolab/etc/rc.d/rc.kolab start
+
+Note 1: Please watch carefully the output when installing the kolab rpm.
+You will then see the important manager password on the screen which is
+required for administrating kolab server via webinterface.
+
+ https://kolabserver.yourdomain.com/admin
+
+Note 2: Note that kolab startup takes its time. Just give it some seconds and watch the
syslog in the meantime. It should all come up nicely.
-Note 4: For your convinience we also uploaded Debian 3.0 packages of the kolab server. Please be aware of the
-fact that only the source distribution is officially supported by us.
+On Linux the output of "netstat -ntplou" gives you an idea which services got
+activated.
+
+===========================================================================
+
+
+Regards,
+--martin
+<martin.konold at erfrakon.de>
Regards,
--martin
More information about the devel
mailing list