For some unknown reason, I neglected to post links to my newest round of upgrade tutorials on this site (and instead focused only on vBulletin.com), sorry.
For those of you wanting to upgrade to httpd 2.2.4, check out my tutorial at the link below. Keep in mind that rebuilding httpd will require you to recompile PHP, mod_perl, etc. so if you use this guide, I also suggest that you check out my other tutorials for PHP, MySQL, XCache, etc.
[url=http://www.jasonlitka.com/2007/01/17/upgrading-to-httpd-224-on-rhel-centos-4/]Upgrading to httpd 2.2.4 on RHEL and CentOS 4[/url]
How-To: Upgrade to httpd 2.2.4 w/ RPMs on RHEL/CentOS 4
-
- Posts: 80
- Joined: 2006/09/11 14:35:48
- Location: Exton, PA
- Contact:
Re: How-To: Upgrade to httpd 2.2.4 w/ RPMs on RHEL/CentOS 4
Hi Jasonxoxide,
I was thinking about getting httpd as source tar.gz from apache.org and PHP from php.net. What are the advantages of using SRPMs for this?
And, if you've got another second - no matter what I try, when I build Apache 2.2.4 from source, the config directory is always under the install directory and never under /etc/httpd like the build that came with centos. Do you have a clue how I need to configure it to go there?
I appreciate it,
Helzer
I was thinking about getting httpd as source tar.gz from apache.org and PHP from php.net. What are the advantages of using SRPMs for this?
And, if you've got another second - no matter what I try, when I build Apache 2.2.4 from source, the config directory is always under the install directory and never under /etc/httpd like the build that came with centos. Do you have a clue how I need to configure it to go there?
I appreciate it,
Helzer
How-To: Upgrade to httpd 2.2.4 w/ RPMs on RHEL/CentOS 4
[quote]
helzer wrote:
Hi Jasonxoxide,
I was thinking about getting httpd as source tar.gz from apache.org and PHP from php.net. What are the advantages of using SRPMs for this?
And, if you've got another second - no matter what I try, when I build Apache 2.2.4 from source, the config directory is always under the install directory and never under /etc/httpd like the build that came with centos. Do you have a clue how I need to configure it to go there?
I appreciate it,
Helzer[/quote]
The benefit of using SRPMS is that you can control where config directory will go (for example) and it will be esy to uninstall if it does not work, same goes for upgrade... not to forget dependencies issues and how you can distribute the new version over a server farm.
helzer wrote:
Hi Jasonxoxide,
I was thinking about getting httpd as source tar.gz from apache.org and PHP from php.net. What are the advantages of using SRPMs for this?
And, if you've got another second - no matter what I try, when I build Apache 2.2.4 from source, the config directory is always under the install directory and never under /etc/httpd like the build that came with centos. Do you have a clue how I need to configure it to go there?
I appreciate it,
Helzer[/quote]
The benefit of using SRPMS is that you can control where config directory will go (for example) and it will be esy to uninstall if it does not work, same goes for upgrade... not to forget dependencies issues and how you can distribute the new version over a server farm.