martin: server/doc QIM,1.15.2.21,1.15.2.22

[cvs at intevation.de]

Author: martin

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

Modified Files:
      Tag: KOLAB_1_0
	QIM 
Log Message:
Martin K.: Updated for testing, will later move to stable Kolab 1.0. Updated
security relevant openssl, proftpd, perl, perl-www, postfix


Index: QIM
===================================================================
RCS file: /kolabrepository/server/doc/QIM,v
retrieving revision 1.15.2.21
retrieving revision 1.15.2.22
diff -u -d -r1.15.2.21 -r1.15.2.22
--- QIM	13 Aug 2003 13:20:17 -0000	1.15.2.21
+++ QIM	30 Sep 2003 23:32:42 -0000	1.15.2.22
@@ -1,4 +1,4 @@
-Quick Install Manual - Kolab 1.0.4
+Quick Install Manual - Kolab 1.0.14
 Author: Martin Konold <martin.konold at erfrakon.de>
 $Id$
 
@@ -20,8 +20,8 @@
 ========================================================================
 Important!
 
-We do currently depend on the latest unstable OpenPKG Current - As soon as
-available we will port to the very soon expected OpenPKG 1.3. Actually OpenPKG is
+We do currently depend on some older OpenPKG version  - As soon as
+possible we will port to the alread released OpenPKG 1.3. Actually OpenPKG is
 already very reliable so that this circumstance should not really matter to
 Kolab users currently.
 
@@ -44,7 +44,9 @@
 than a single directory. You may use symbolic links as a workaround. This will
 change when we move to OpenPKG 1.3 and release Kolab 1.1. If you decide for a
 different prefix than /kolab please adopt the instruction appropriatly. Using
-the /kolab prefix allows for simple copy&paste.
+the /kolab prefix allows for simple copy&paste. 
+
+We are very much interested what breaks in case of a prefix different from /kolab.
 
 =======================================================================
 ==================== Installation from Source =========================
@@ -116,7 +118,7 @@
 
 cd  /kolab/RPM/SRC/PACKAGE
 rpm -bb PACKAGE.spec
-(becoming root for installing the rpms is required because we install daemon services. 
+(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
 
@@ -166,7 +168,7 @@
 define statement. The later is mandatory for a functional Kolab server.
 
 (Please make sure that you use the correct OpenPKG rpm executable when building
-the packages and installing!)
+the packages and installing! You may check this issueing the command `which rpm`)
 
 rpm -ba gdbm.spec --define 'with_ndbm yes'
 rpm -Uvh /kolab/RPM/PKG/gdbm*kol.rpm
@@ -262,7 +264,7 @@
 /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 openssl-0.9.7b-20030530.ix86-linux2.4-kol.rpm
+/kolab/bin/rpm -Uhv openssl-0.9.7b-20030930.ix86-linux2.4-kol.rpm
 /kolab/bin/rpm -Uhv perl*.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
@@ -306,6 +308,8 @@
 syslog in the meantime. It should all come up nicely.
 
 On Linux the output of "netstat -ntplou" gives you an idea which services got
-activated.
+activated. You may use this command also in order to make sure that no service 
+is blocking and port when kolab is stopped. E.g. the MTA as provided by the vendor
+of the operating system might already use port 25.
 
 ===========================================================================