restoring head

diff --git a/doc/INSTALL.mir b/doc/INSTALL.mir
index 215b9c3..7e23976 100755 (executable)
--- a/doc/INSTALL.mir
+++ b/doc/INSTALL.mir
@@ -1,6 +1,6 @@
 MIR INSTALLATION HOWTO
 
-Last updated: $Date: 2003/09/03 18:29:00 $
+Last updated: $Date: 2004/11/06 17:47:26 $
 ----------------------------------------------------------------
 
 Here is a short installation-howto of Mir.
@@ -15,10 +15,10 @@ prerequisites:
 - postgres 7.1+
 - ant (a java-based make) 
 - jaxp-1.1 (a SAX 2.0 compliant XML parser, comes with ant >= 1.4)
-- the JAI image framework (Java Advanced Imaging) versin 1.1.1 . get it from 
-  java.sun.com. ** NOTE: because JAI uses a native acceration library (a .so)
-  it must be placed in tomcat's "lib" (i.e $TOMCAT_HOME/common/lib) directory and
-  not under the default webapps/Mir/WEB-INF/lib directory **
+- the JAI image framework (Java Advanced Imaging) version 1.1.2 . Get it from 
+  java.sun.com. You need both: JAI and JAI Image I/O. Install those two in
+  the JRE running tomcat.
+
 - A good reading of Tomcat, Apache and Postgresql documentation if you are not
   familiar with any of them. The documentation is available at:
   http://jakarta.apache.org/tomcat/tomcat-4.0-doc/index.html,
@@ -85,17 +85,13 @@ This is practical if you are running several installations of mir on one
 tomcat or other webapps and can't afford to shutdown all of them.
 See the tomcat documentation to learn how to enable and use the manager app.
 
-7. Copy any dynamic library files ending with ".so" (so far only the JAI native
-acceleration library found in the JAI package tarball or zip from sun) to your
-$JAVA_HOME/jre/lib/i386 directory (where the other ".so" files live). Or, you
-can skip the whole thing and live without "native" acceleration for image
-manupulation.
+7. Follow the installation instructions of JAI / JAI Image I/O.
 
 8a. create a new database 
 The database name should be the same as in config.properties. Please look at
 the section "Database.*" to look up the names or change them to your needs. 
 
-It is wise in terms of system seurity to use an unprivileged user for this
+It is wise in terms of system security to use an unprivileged user for this
 task instead of the superuser. This is because if Mir uses the superuser to
 connect to the database and anybody manages to find out the password Mir 
 uses to connect, the attacker can take over the complete database. So, in
@@ -260,4 +256,4 @@ You can give these a try if anything goes wrong:
 
 ----------------------------------------------------------------
 
-$Date: 2003/09/03 18:29:00 $ - the Mir coders
+$Date: 2004/11/06 17:47:26 $ - the Mir coders

diff --git a/doc/LOCALIZER.HOWTO b/doc/LOCALIZER.HOWTO
index c0a0fcf..c1d5013 100755 (executable)
--- a/doc/LOCALIZER.HOWTO
+++ b/doc/LOCALIZER.HOWTO
@@ -1,4 +1,4 @@
-Version: $Date: 2004/11/06 16:01:25 $
+Version: $Date: 2004/11/06 17:47:26 $
 
 This is the HOWTO of the Localization infrastructure 
 which allows easy low-level customization of Mir.

diff --git a/doc/MAINTENANCE.postgresql b/doc/MAINTENANCE.postgresql
index 8355d3b..434a87f 100755 (executable)
--- a/doc/MAINTENANCE.postgresql
+++ b/doc/MAINTENANCE.postgresql
@@ -7,7 +7,7 @@ To dump the database use pg_dump
 
 To restore do the following
 
-  pg_restore -d [name_of_database] -u [dbuser] -Ft dump.tar 
+  pg_restore -d [name_of_database] -U [dbuser] -Ft dump.tar 
 
 
 VACUUM and VACUUM ANALYZE
@@ -25,3 +25,4 @@ USER MANAGMENT IN POSTGRESQL
 
 If you want to change the db user of a mir db, there's a script for 
 that in mir/dbscripts/extra.
+

diff --git a/doc/README b/doc/README
index 5653316..e3f3a82 100755 (executable)
--- a/doc/README
+++ b/doc/README
@@ -1,4 +1,4 @@
-last changed $Date: 2002/12/24 01:45:54 $
+last changed $Date: 2004/11/06 17:47:26 $
 -----------------------------------------
 
 GENERAL INFO
@@ -83,6 +83,6 @@ In the upcoming 1.1 release
 * completely rewrite of the producer layer. Runs in it's own thread.
   Configurable via an XML file to dynamically choose the structure the site
   should take, what should be archived...
-* Introduction of the Localization infracstructure to allow easy low-level
+* Introduction of the Localization infrastructure to allow easy low-level
   customization of Mir.