eBox configuration management

[Matt Zimmerman]

If I understand correctly, you have two different cases related to
configuration files which must be resolved:

1. Configuring packages eBox needs to work (at least slapd, are there
others?)

2. Configuring packages in response to web configuration requests from an
administrator

For #1, some of the options are, in approximately descending order of
preference:

- Make the configuration unnecessary by making the default configuration
  suitable for ebox (simplest)

- Perform configuration using a ".d" idiom, where you only need to add files
  and reload the configuration (ok)

- Use an alternate configuration file (e.g., LTSP and dhcp3-server)
  (confusing)

- Use non-conffile configuration files, and modify them in the ebox
  maintainer scripts (fragile)

For #2, the simplest thing to do is, as you say, to ask the user for
confirmation before clobbering the file.  This allows administrators the
freedom to modify configuration files by hand, while retaining the ability
to use the web interface, and follows the principle of least surprise by
mimicking what is done elsewhere in the system.

-- 
 - mdz