From 95dfac5bbf011f45375b99426e7940991ff3eb1b Mon Sep 17 00:00:00 2001
From: root
Date: Sun, 24 Nov 2013 16:53:17 +0100
Subject: Small changes, comments for doc/ ...

---
 doc/setup_howto | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

(limited to 'doc/setup_howto')

diff --git a/doc/setup_howto b/doc/setup_howto
index 8ab927d2..23819d11 100644
--- a/doc/setup_howto
+++ b/doc/setup_howto
@@ -62,13 +62,15 @@ for delivery.
 Build Stage31:
 # ./mltk remote stage31 -c -b (-d -> debug when appropriate)
 
+... this will take quite some time, mostly due to kernel compiling.
+
 Build Stage32:
 # ./mltk remote stage32 -c -b (-d )
 
 Build Stage32 for openSuse:
 # ./mltk remote stage32-opensuse -c -b
 
-... this will take some time, mostly due to kernel compiling.
+... this will take some time, mostly due to compiling a couple of packages.
 
 
 Building a single module:
@@ -103,6 +105,8 @@ server machine via rsync. To facilitate this rsync-ing it may be wise to
 add the ssh key to the build machine (authorized_keys), as then no password 
 has to be given when syncing from the server machine.
 
+## Das würde ich für die Zukunft als Default annehmen. Das andere ist ja eher
+## zum Testen in sehr kleinem Setup.
 So, remember to execute
 # ./mltk remote -n
 on the build machine, if the build is going to by synchronized to a dedicated 
@@ -127,6 +131,7 @@ To package addons the parameter 'addons' has to be used:
 
 First, do a
 # ./mltk server [IP a build machine] -s
+
 to synchronize all stage/addon builds in one pass. This synchronizes the 
 complete build directories from the remote (build) machine to the server. 
 It is possible to synchronize several build machines (thus different 
-- 
cgit v1.2.3-55-g7522