[doc] update doc, add doc for kcl vars

1 files changed, 25 insertions, 13 deletions

diff --git a/doc/setup_howto b/doc/setup_howto
index e520973e..00dc012d 100644
--- a/doc/setup_howto
+++ b/doc/setup_howto
@@ -194,12 +194,34 @@ will be defined here. These parameters are documented in doc/boot_config_vars.
 The file config.tgz holds localization information for specific environments, 
 e.g. specific local authentification, home directories, shares and the like. 
 If there is no pre-formatted localization available it's perhaps a good 
-idea to just touch config.tgz or pack an empty archive of that name. Example 
-localizations may be listed at [path to tm-scripts]/server/configs.
+idea to just touch config.tgz or pack an empty archive of that name. 
+
+Example localizations may be listed at [path to tm-scripts]/server/configs.
+As with the stages, the configs are based on modules. That way you can easily
+link to existing modules and add own configuration modules to 
+[path to tm-scripts]/server/modules if needed.
+
+To automatically pack one of the configs under [path to tm-scripts]/server/configs 
+run the openslx script as follows:
+
+# ./openslx <IP of build machine> -k <config_name>
+
+An archive will be created under [path to tm-scripts]/server/boot/[IP or local]/config.tgz
+As mentioned above you can link or copy it into your webroot dir.
 
 
 10. iPXE: TODO
 
+Currently we use iPXE to deliver kernel and initramfs at boot time via HTTP.
+That is also the reason why kernel and initramfs are provided on a webroot instead of a 
+classical tftp directory. 
+
+iPXE can be downloaded here: http://ipxe.org/
+Download and compile the source as described on the homepage.  
+
+
+
+
 This will be most probably not being required in the future, as relevant 
 features are available in recent Syslinux versions (6.0.0+).
 
@@ -217,18 +239,8 @@ will be accessed client-side by nfs. Please keep in mind that
 "./mltk -n" has to be executed on the build machine before cloning 
 Stage 4.
 
-Then, be sure all builds are synced to the server machine, if that has not 
-happened before:
-# ./openslx <IP of build machine> -s
-
-... or, if wanted, sync just some parts, if you know what you're doing. 
-Stage31 makes most sense so far, so to say. So, for example:
-# ./openslx <IP> stage31 -e cpio -s
-etc.
-
 Well, then do the cloning work:
-# ./scripts/clone_stage4 [IP of build machine] stage32 \
-	/path/to/your/nfs/share/stage4     # (this is one line!)
+# ./scripts/clone_stage4 [IP of build machine] /path/to/your/nfs/share/stage4
 
 To use Stage 4 the clients need the nfs mount information. This is handled via 
 a configuration variable (please consult doc/boot_config_vars for a full