diff options
| author | Christian Rößler | 2013-11-24 17:44:24 +0100 |
|---|---|---|
| committer | Christian Rößler | 2013-11-24 17:44:24 +0100 |
| commit | 9dc425e2ea657696457318c0033c61e9f3116652 (patch) | |
| tree | 386fd1d90e1ad6b717b44114ad56498b023589ee /doc | |
| parent | [doc] setup_howto: option -d when compiling kernel kernel (diff) | |
| parent | Small changes, comments for doc/ ... (diff) | |
| download | tm-scripts-9dc425e2ea657696457318c0033c61e9f3116652.tar.gz tm-scripts-9dc425e2ea657696457318c0033c61e9f3116652.tar.xz tm-scripts-9dc425e2ea657696457318c0033c61e9f3116652.zip | |
Merge branch 'master' of git.openslx.org:openslx-ng/tm-scripts
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/setup_howto | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/setup_howto b/doc/setup_howto index 547910bb..abc7e2bb 100644 --- a/doc/setup_howto +++ b/doc/setup_howto @@ -64,13 +64,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: @@ -105,6 +107,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 @@ -129,6 +133,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 |
