aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorLudovic Courtès <ludo@gnu.org>2013-08-24 11:08:01 +0200
committerLudovic Courtès <ludo@gnu.org>2013-08-24 17:30:31 +0200
commitb095792f9b8676411f7b5eb6c768d28ae123449b (patch)
tree5b09feeeb215ab1457b2295a8b15c3b669d38039 /doc
parentc9dfa3c72184fcad6a4c1c23d5c75c6d01b77a8c (diff)
downloadguix-b095792f9b8676411f7b5eb6c768d28ae123449b.tar.gz
guix-b095792f9b8676411f7b5eb6c768d28ae123449b.zip
doc: Mention what's in the chroot, and add a caveat about /dev/shm.
* doc/guix.texi (Setting Up the Daemon): Document the default content of the chroot, and the /dev/shm caveat.
Diffstat (limited to 'doc')
-rw-r--r--doc/guix.texi11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/guix.texi b/doc/guix.texi
index 684382720e..57b6412939 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -244,6 +244,17 @@ The @code{guix-daemon} program may then be run as @code{root} with:
# guix-daemon --build-users-group=guix-builder
@end example
+@noindent
+This way, the daemon starts build processes in a chroot, under one of
+the @code{guix-builder} users. On GNU/Linux, by default, the chroot
+environment contains nothing but the @code{/dev} and @code{/proc}
+directories@footnote{On some systems @code{/dev/shm}, which supports
+shared memory, is a symlink to another directory such as
+@code{/run/shm}, that is @emph{not} is the chroot. When that is the
+case, shared memory support is unavailable in the chroot environment.
+The workaround is to make sure that @file{/dev/shm} is directly a
+@code{tmpfs} mount point.}.
+
Guix may also be used in a single-user setup, with @command{guix-daemon}
running as an unprivileged user. However, to maximize non-interference
of build processes, the daemon still needs to perform certain operations