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.
This commit is contained in:
parent
15650ac2a0
commit
efa77c6c92
|
@ -6048,8 +6048,9 @@ Next, you have to edit a file and
|
||||||
provide the declaration of the operating system to be installed. To
|
provide the declaration of the operating system to be installed. To
|
||||||
that end, the installation system comes with two text editors: GNU nano
|
that end, the installation system comes with two text editors: GNU nano
|
||||||
(@pxref{Top,,, nano, GNU nano Manual}), and GNU Zile, an Emacs clone.
|
(@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
|
We strongly recommend storing that file on the target root file system, say,
|
||||||
@file{/mnt/etc/config.scm}.
|
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
|
@xref{Using the Configuration System}, for an overview of the
|
||||||
configuration file. The example configurations discussed in that
|
configuration file. The example configurations discussed in that
|
||||||
|
|
Loading…
Reference in New Issue