From efa77c6c92d47f7eab5827681e83a94bc3cc7a8c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ludovic=20Court=C3=A8s?= Date: Mon, 28 Mar 2016 22:02:37 +0200 Subject: [PATCH] doc: Explain why the config file should be stored on the target. Suggested by Chris Marusich . * doc/guix.texi (Proceeding with the Installation): Explain why the config file should be on the target file system. --- doc/guix.texi | 5 +++-- 1 file 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