On Tue, Nov 02, 2004 at 10:04:46PM +0100, Josephine wrote:
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
Not really true -- the apache 2.0 default ("example" !) configuration file from upstream is not so much different from the apache 1.3 one. But as I said in the other mail, while SuSE split it some time ago a very similar splitting will happen upstreams as well, in the future. Peter