Re: [cobalt-developers] Apache 1.3.20 upgrade list of supported packages?

["William L. Thomson Jr." <wlt@xxxxxxxxxxxxxxxxxxxx>]

Michelle,
	Compiling modules for Apache on RaQ's is no different than compiling 
modules for a regular apache.  If you are needing modules that aren't 
there, what I do is obtain apache source code of the same version that 
is on you machine, and compile what ever modules are needed.  You should 
be able to do this without the entire source code, with just the source 
code from the needed modules and use the apxs utility to compile shared 
objects/modules for apache.  Here is a few links

http://httpd.apache.org/docs/programs/apxs.html

http://httpd.apache.org/docs/dso.html

The needed .h files should be in /usr/include/apache

I have not tried this on a Raq. I usually obtain the entire source, and 
compile and entire apache so I can test the modules against the proper 
version. Then if it works I upload and replace/add the module to the RaQ.

For anyone who needs them, I keep a variety of compiled modules on our 
FTP server for public use.  I have heard some complaints about the 
modules not being complied with EAPI, but they should be.

ftp://ftp.obsidian-studios.com/support/software/apache/


As for ChiliSoft ASP, version 3.5.X was supposed to only support up to 
Apache 1.3.14 and I have it working perfectly with versions up to Apache 
1.3.20.  As for ChiliSoft ASP 3.6, I would imagine worse case you will 
have to compile your own module for Apache 1.3.20. I cannot see it not 
working at all, unless there are other differences other that what they 
say there are.



Michelle A. Hoyle wrote:

> When I moved from my Raq2 to my Raq4, I was shocked to discover that the 
> Raq4's version of Apache had been compiled without modules for 
> mod_auth_db and mod_auth_dbm, both of which I'm heavily using for 
> controlling access to large sites on my Raqs.  I had to pay Cobalt 
> Development Services $600 US (that was my half -- someone else needed 
> the same modifications) to produce me a version that included *all* the 
> standard Apache modules because, at the time, there was very little 
> information available on how to compile Apache yourself for the various 
> Raqs.
>
> Given my past history with unexpected results with Apache changes, you 
> can understand my reluctance to upgrade to 1.3.20, even though I've been 
> waiting since the vulnerability was announced for an upgrade package.
>
> What I'd like to know is where can I find a list of supported modules 
> for this Apache upgrade without installing it (which, apparently, is a 
> bad idea  problem with Chili!Soft?) first?
>
>
> Thanks,
>
> Michelle A. Hoyle


--
Sincerely,
William L. Thomson Jr.
Obsidian-Studios Inc.
439 Amber Way
Petaluma, Ca. 94952
Phone/fax 707.766.9509
http://www.obsidian-studios.com