Josephine wrote:
On Tuesday 02 November 2004 19:27, Jordan Michaels wrote:
Can anyone give me a definitive answer on this?
Perhaps, but not that I've seen. We do a lot of work with CentOS 3.1 because of it's compatibility with RHEL and it's httpd.conf is NOT broken up in to thousands (yes, I'm exaggerating) of includes. It's just one file, which, honestly, seems simpler to me then the hordes of includes.
I know, and I did. It would just save us many, many hours if we didn't have to talor it for every server that we set up. Time is money and SuSE is starting to take more of it! *NOT* cool! I'm a big fan of SuSE and have been for a long time - but this bothers me. It'd be nice to have the option of the default install being just one file.
You really need a deep look into the apache documentation for both apache 1.3 and apache 2.0. You need to understand that this is no *fault* from suse, nor a bug or a *feature* that the httpd.conf is different from what you knew on suse 9.0. It is simply apache2 and *exactly* that is the way httpd.conf should look. If you dislike apache2 for the way it handles configuration, you are free to install binaries/whatever for apache 1.3.x and play with the httpd.conf you are used with. But please understand that SuSE is just trying to offer you the latest releases and they are not inventing configuration files for most common services. Learn it or change it to something you know, but don't blame suse for trying to give you latest stuff.
Josephine
My Apologies. I meant no offense. SuSE is and has been my favorite distro for several years now. I think they do excellent work. I was unaware that this was the default apache standard. Now that I know that (you learn something new every day!), I'm sure more and more third-party applications will be able to use the new configuration structure. I guess I was just a little frustrated that they don't already. =\ Thanks for understanding. -- Warm regards, Jordan Michaels Vivio Technologies http://www.viviotech.net/ jordan@viviotech.net