You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by sl...@apache.org on 2005/11/29 16:57:47 UTC

svn commit: r349744 - /httpd/httpd/branches/2.2.x/docs/manual/upgrading.xml

Author: slive
Date: Tue Nov 29 07:57:45 2005
New Revision: 349744

URL: http://svn.apache.org/viewcvs?rev=349744&view=rev
Log:
The module name changes will probably hit people in
run-time configuration at least as much as in
compile-time, so mention it there as well.

Modified:
    httpd/httpd/branches/2.2.x/docs/manual/upgrading.xml

Modified: httpd/httpd/branches/2.2.x/docs/manual/upgrading.xml
URL: http://svn.apache.org/viewcvs/httpd/httpd/branches/2.2.x/docs/manual/upgrading.xml?rev=349744&r1=349743&r2=349744&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/upgrading.xml (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/upgrading.xml Tue Nov 29 07:57:45 2005
@@ -71,7 +71,12 @@
     <p>Your existing version 2.0 config files and startup scripts can
       usually be used unchanged in version 2.2.  Some small
       adjustments may be necessary for particular configurations as
-      discussed below.  If you choose to use the new default
+      discussed below.  In addition, if you dynamically load the
+      standard modules using the <directive
+      module="mod_so">LoadModule</directive> directive, then you will
+      need to account for the module name changes mentioned above.</p>
+
+    <p>If you choose to use the new default
       configuration file for version 2.2, you will find that it has
       been greatly simplified by removing all but the most essential
       configuration settings.  A set of example configuration settings