Seema Alevoor wrote: > > Fine. Let us have conf.d (new empty directory) under /etc/apache2 .
Why would it be empty? If that's the one and only editable conf directory, surely there will be something there? If you look at the apache2 currently in the sources, a number of conf files are installed, some are copied as-is and some are copied with modifications. All those files, at least (or more - since a goal of Web Stack is to enhance functionality and improve out of box experience) will be there in the directory containing conf files. Could you expand on why you see conf.d being empty? > >P.S. Since extra contains only examples from the src distro, I'd > >rather see it under /usr somewhere, to correctly reflect the files are > >static, not editable configuration. > > Let us not move "extra" out of /etc/apache2 since this contains only example > configuration files and /etc/apache2 is the directory related to server > configuration. > The initial set of permissions can be changed from 644 to 444. And all the > .conf > files within extra dir should be renamed to .conf-example. -1! I definitely don't like the idea of both /etc/apache2/conf.d/ and /etc/apache2/extra/. That's what I'm seeking to avoid here, it's clutter and confusing. Let's pick one. A customer should not have to go read man pages to figure out where to edit files. Renaming the files under extra to *-example doesn't help that much. If I rename extra/foo.conf-example to extra/foo.conf will it start to work? (answer is no, but that's not obvious by looking at such a directory structure). Currently there is /etc/apache2/original/extra/ containing as-is files from the sources. That's the directory I was thinking about. An option is to leave it there for that purpose or move it somewhere under /usr/apache2. On this I could see it either way, but I slightly prefer /usr because it contains static files that are never meant to be changed after install. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
