Upgrade from Apache 1.3.27 to 2.0.50 (Solaris 8)

Preface: A rather newbie to unix, and a definite newbie to Apache
server.

In any case, I have a Solaris 8 server that currently is running :

Server version: Apache/1.3.27 (Unix)
Server built: Nov 5 2003 16:34:08

With that said, I've been tasked to upgrade to Apache 2.0. Before I
get started, what might be the things to considered to be good
practice before I implement this upgrade? Naturally, the system is
backed up nightly but are there any files that I should print that
might help in reconfiguring the upgraded Apache server to mimic the
current 1.3.27 configuration? Is there any other software that I might
need to implement this upgrade? The version of gcc that I have is
2.95.2. Are there any systems files that I need to edit before I
perform the upgrade? How do I ensure that the server is running only
the 2.0 version when the upgrade is completed? Any other questions I
haven't anticipated? Or any suggestions or tips from the more
experienced Apache users?



The current 1.3.27 version has apache DIRS in the following areas:

/usr/local/apache
/usr/apache
/usr/apache/jserv/docs/api/org/apache
/etc/apache
/var/apache

When I copy the httpd-2.0.50.tar.gz file to the server, does it matter
that I copy this file to the /opt DIR to uncompress, and untar this
file? From the above, it appears to be a default installation. In
other words, does the above indicate that at the initial build there
was not an atypical (or no prefix added to the .configure commend)?
How do I find out if the install of v. 1.3.27 had flag taged to the
..configure which I would need to reapply to the .configure of the
upgrade to 2.0? How do I know if which module was compiled with v
1.3.27 that need to be add to the upgrade to 2.0? I performed a find
for the source tree (config.nice ?) on the current system but there
appears not to be one. This Java do I need to change the link to
apache to point to apache2? I would prefer not to have to version
running on the server. Again, I thank you for all help.

Sincerely,

-verO

In article <b58d52cb.0407291126.29a8cd7a@posting.google.com >,
VerO <veronique.platz@belvoir.army.mil> wrote:
>Preface: A rather newbie to unix, and a definite newbie to Apache
>server.
>
>In any case, I have a Solaris 8 server that currently is running :
>
>Server version: Apache/1.3.27 (Unix)
>Server built: Nov 5 2003 16:34:08
>
>With that said, I've been tasked to upgrade to Apache 2.0. Before I
>get started, what might be the things to considered to be good
>practice before I implement this upgrade? Naturally, the system is
>backed up nightly but are there any files that I should print that
>might help in reconfiguring the upgraded Apache server to mimic the
>current 1.3.27 configuration? Is there any other software that I might
>need to implement this upgrade? The version of gcc that I have is
>2.95.2. Are there any systems files that I need to edit before I
>perform the upgrade? How do I ensure that the server is running only
>the 2.0 version when the upgrade is completed? Any other questions I
>haven't anticipated? Or any suggestions or tips from the more
>experienced Apache users?
>
>
>
>The current 1.3.27 version has apache DIRS in the following areas:
>
>/usr/local/apache
>/usr/apache
>/usr/apache/jserv/docs/api/org/apache
>/etc/apache
>/var/apache
>
>When I copy the httpd-2.0.50.tar.gz file to the server, does it matter
>that I copy this file to the /opt DIR to uncompress, and untar this
>file? From the above, it appears to be a default installation. In
>other words, does the above indicate that at the initial build there
>was not an atypical (or no prefix added to the .configure commend)?
>How do I find out if the install of v. 1.3.27 had flag taged to the
>.configure which I would need to reapply to the .configure of the
>upgrade to 2.0? How do I know if which module was compiled with v
>1.3.27 that need to be add to the upgrade to 2.0? I performed a find
>for the source tree (config.nice ?) on the current system but there
>appears not to be one. This Java do I need to change the link to
>apache to point to apache2? I would prefer not to have to version
>running on the server. Again, I thank you for all help.
>
>Sincerely,
>
>-verO

The way I did it was compile 2.0

Move old httpd.conf to a backup position

install

merge new and old httpd.conf files
--
Member - Liberal International
This is doctor@nl2k.ab.ca Ici doctor@nl2k.ab.ca
God Queen and country! Beware Anti-Christ rising!
Microsoft is not the solution; it is the question; what is the answer?? NO!!