* Approaches like SunFreeware or Blastwave are far far away from
being something like what I'm proposing. It is not the same
league; it is not even the same game. Sorry. :-)
Just out of curiosity, why do you say that (for Blastwave at least)?
I'm not sure I would have phrased it in those words (after all, part of a
being in a community means being tactful and polite), but debian encompasses
a lot of architectural policy that sfw/csw don't. To be fair, one of the
reasons that they don't is that they are piggybacking on top of the
already-defined architecture from Solaris. Since it already exists,
SunFreeware and Blastwave didn't need to reinvent those particular wheels :-)
Debian has done good things with setting up and maintaining a distinction
between runtime -vs- compile time module/component configuration mechanisms,
installation locations, etc.
As an example, look at debian's apache2 installation and configuration - the
conf files are all set up for a modular multi-site system, with configuration
and feature selection done by symlinking instead of editing files. (I've
included the apache2 README below to give a flavor of this perspective).
IMHO, it is the systems level thought and integration that makes
Debian more than simply a collection of pre-built packages. Obviously, I
have been quite impressed by the thought and effort that has gone into the
Debian system, and agree with David that OpenSolaris could benifit from it.
-John
Debian's default Apache2 installation attempts to make adding and
removing modules, virtual hosts, and extra configuration directives as
flexible is possible, in order to make automating the changes and
administering the server as easy as possible.
Files and Directories in /etc/apache2:
-------------------------------------
apache2.conf
This is the main configuration file.
conf.d/
Files in this directory are included by this line in
apache2.conf:
# Include generic snippets of statements
Include /etc/apache2/conf.d
This is a good place to add additional configuration
directives.
httpd.conf
Empty file.
mods-available/
This directory contains a series of .load and .conf files.
The .load files contain the Apache configuration directive
necessary to load the module in question. The respective
.conf files contain configuration directives necessary to
utilize the module in question.
mods-enabled/
To actually enable a module for Apache2, it is necessary to
create a symlink in this directory to the .load (and .conf, if
it exists) files associated with the module in
mods-available/. For example:
cgi.load -> /etc/apache2/mods-available/cgi.load
ports.conf
Configuration directives for which ports and IP addresses to
listen to.
sites-available/
Like mods-available/, except it contains configuration
directives for different virtual hosts that might be used with
apache2. Note that the hostname doesn't have to correspond
exactly with the filename. 'default' is the default host.
sites-enabled/
Similar in functionality to mods-enabled/, sites-enabled
contains symlinks to sites in sites-available/ that the
admnistrator wishes to enable.
Example:
dedasys -> /etc/apache2/sites-available/dedasys
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
