Jason, That doesn't really sounds like "the SuSE way", but I guess it's close enough.. :) One question pops up though, what happens with that config-change if the customer decides to do an upgrade? Will it stick? Anyway, it's such a simple thing to include that little thing in the documentation I'll include with the system at delivery. Another guy here (sorry, I can't recall your name) told me he's read at the php home site that they suggest that Apache2 and php isn't really stable enough for a production environment, and since this particular system IS going to a production env, it's imperative that it's as stable as a rock.. Which a "un-tweaked" SuSE system is in 99.9% of the installations I've made throughout the years. Anders Norrbring Norrbring Consulting
I was able to duplicate your problem on an 8.2 box. After installing the apache2 and php4 stuff and doing no configuration, attempts to access a test php page resulted in a dowload dialogue. Edit the file "/etc/sysconfig/apache2" and add "libphp4" to the APACHE_MODULES line. If you don't change anything else, it'll look like this:
APACHE_MODULES="access actions alias auth auth_dbm autoindex cgi dir env expires include libphp4 log_config mime negotiation setenvif status suexec userdir"
Then run the SuSEconfig command and restart apache2. Php pages should load up fine.
Jason ===========