aboutsummaryrefslogtreecommitdiff
path: root/doc/manual.cli
diff options
context:
space:
mode:
Diffstat (limited to 'doc/manual.cli')
-rw-r--r--doc/manual.cli16
1 files changed, 13 insertions, 3 deletions
diff --git a/doc/manual.cli b/doc/manual.cli
index 3abd639..7284c6a 100644
--- a/doc/manual.cli
+++ b/doc/manual.cli
@@ -36,7 +36,9 @@ mode} and receive \i{build tasks} from their respective agents.
Build OS root filesystem (\c{rootfs}) resides entirely in RAM with all changes
(such as installation of the \c{build2} toolchain} discarded on the next
reboot. A small amount of persistent (but not precious) state is stored in
-\c{/state} (see \l{#config-storage-state State}).
+\c{/state} (see \l{#config-storage-state State}). A minimum of 4G of RAM
+is required for Build OS itself (that is, excluding any virtual machines
+and containers).
After booting the kernel, the Build OS execution starts with a custom \c{init}
script which performs low-level configuration and setup and then hands off the
@@ -339,10 +341,18 @@ e723[...]c305 *0.4.0/build2-mingw-0.4.0-x86_64-windows.tar.xz
Based on the checksums file the monitor downloads each file into
\c{/build/tftp/toolchain/<name>/} (the file path is taken as relative to
\c{toolchain_url}), verifies their checksums, and creates \i{predictable name}
-symlinks (names without the version). Continuing with the above example, the
-contents of \c{/build/tftp/toolchain/default/} would be:
+symlinks (names without the version). It also creates the \c{version} which
+contains the toolchain version and the \c{trust} file which contains the
+value of the \c{buildos.toolchain_trust} parameter or the special \c{\"no\"}
+value if none were specified.
+
+Continuing with the above example, the contents of
+\c{/build/tftp/toolchain/default/} would be:
\
+version
+trust
+
build2-toolchain-0.4.0.tar.xz
build2-baseutils-0.4.0-x86_64-windows.zip
build2-mingw-0.4.0-x86_64-windows.tar.xz