aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLudovic Courtès <ludo@gnu.org>2016-03-28 22:02:37 +0200
committerLudovic Courtès <ludo@gnu.org>2016-03-28 22:25:42 +0200
commitefa77c6c92d47f7eab5827681e83a94bc3cc7a8c (patch)
tree5b5327b5daa8ea98477f126e6b3692f9f0f80247
parent15650ac2a0b979af52d16b86b2f47bf40d9d13ee (diff)
downloadpatches-efa77c6c92d47f7eab5827681e83a94bc3cc7a8c.tar
patches-efa77c6c92d47f7eab5827681e83a94bc3cc7a8c.tar.gz
doc: Explain why the config file should be stored on the target.
Suggested by Chris Marusich <cmmarusich@gmail.com>. * doc/guix.texi (Proceeding with the Installation): Explain why the config file should be on the target file system.
-rw-r--r--doc/guix.texi5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/guix.texi b/doc/guix.texi
index 0eea658a13..18de55c81b 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -6048,8 +6048,9 @@ Next, you have to edit a file and
provide the declaration of the operating system to be installed. To
that end, the installation system comes with two text editors: GNU nano
(@pxref{Top,,, nano, GNU nano Manual}), and GNU Zile, an Emacs clone.
-It is better to store that file on the target root file system, say, as
-@file{/mnt/etc/config.scm}.
+We strongly recommend storing that file on the target root file system, say,
+as @file{/mnt/etc/config.scm}. Failing to do that, you will have lost your
+configuration file once you have rebooted into the newly-installed system.
@xref{Using the Configuration System}, for an overview of the
configuration file. The example configurations discussed in that