Martin MC Brown wrote: > > You then configure the module configs to be included by editing the / > etc/conf.d/apache file with the list of -D MODULE elements to include > on the command line.
So editing the file is needed to enable a module/app? One of the goals here is that a baseline level of functionality must "Just Work" merely by installing the relevant package(s). The current model of conf.d combined with including conf.d/*.conf from the default configuration was selected for this purpose. It provides a mechanism for packages [when applicable] to drop a file into conf.d which means it is automatically configured without further interaction required from the user (other than svcadm restart apache22). (Of course, once past the initial exploration stage most users are expected to tweak the config to taste. But that comes later, the initial hook needs to "just work".) -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
