SB2's Configuration & Initialization Redesign: part 1

Motivation: sb2's per-target configuration files will be split to smaller
files (one or more / subsystem) to make it possible to
a) reconfigure parts of the system, without doing a full re-initialization
   with sb2-init and
b) to make it possible to upgrade parts of the configuration automatically
   (previously, a full reinitialization (by sb2-init) has been mandatory
   always when the configuration file format has been changed)

This commit introduces some changes to the configuration infrastructure
that are needed in the future; the old config file system is still used for
all real configuration variables.

First, there are two new helper scripts:
- "sb2-upgrade-config" is called automatically by the "sb2" script whenever
  configuration files need to be updated.
- "sb2-parse-sb2-init-args" is now used to parse the command line of "sb2-init";
  this script is needed by "sb2-upgrade-config", too.

Second, "sb2-init" has changes: in addition to the argument processing, some
checks have been re-ordered etc, but there are no real, functional changes

Third, a configuration log was added. The idea is that every time when the
configuration is changed (by any component, either manually or automatically)
the change should be logged. The log can be displayed by sb2-config (a new
option was added to that)

1 files changed, 3 insertions, 0 deletions

diff --git a/docs/sb2-config.1 b/docs/sb2-config.1
index 07f9614..58e7e59 100644
--- a/docs/sb2-config.1
+++ b/docs/sb2-config.1
@@ -16,6 +16,9 @@ This option sets the default sb2 target. The name of the target will be written
 \-l list targets
 This option lists all available targets in your system. The names listed can be used as a parameter to the -d option.
 .TP
+\-L target_name
+Show configuration log ('-' as target name refers to the default target)
+.TP
 \-f
 Display short help.
 .TP