rekahsoft/guix
1
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity

doc: Recommend nano during installation.

Browse Source 
* doc/guix.texi (Preparing for Installation)
(Proceeding with the Installation): Recommend nano.
This commit is contained in:
Ludovic Courtès 2018-04-04 17:32:25 +02:00
parent 76a77ccaed
commit 81c63cfc6f
No known key found for this signature in database
GPG Key ID: 090B11993D9AEBB5
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/guix.texi
View File

@ -8335,10 +8335,10 @@ ifconfig @var{interface} up
To configure wireless networking, you can create a configuration file To configure wireless networking, you can create a configuration file
for the @command{wpa_supplicant} configuration tool (its location is not for the @command{wpa_supplicant} configuration tool (its location is not
important) using one of the available text editors such as important) using one of the available text editors such as
@command{zile}: @command{nano}:
@example @example
zile wpa_supplicant.conf nano wpa_supplicant.conf
@end example @end example
As an example, the following stanza can go to this file and will work As an example, the following stanza can go to this file and will work
@ -8519,8 +8519,10 @@ builds to @file{/gnu/store} which, initially, is an in-memory file system.
Next, you have to edit a file and 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 three text editors: GNU nano that end, the installation system comes with three text editors. We
(@pxref{Top,,, nano, GNU nano Manual}), GNU Zile (an Emacs clone), and recommend GNU nano (@pxref{Top,,, nano, GNU nano Manual}), which
supports syntax highlighting and parentheses matching; other editors
include GNU Zile (an Emacs clone), and
nvi (a clone of the original BSD @command{vi} editor). nvi (a clone of the original BSD @command{vi} editor).
We strongly recommend storing that file on the target root file system, say, 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 as @file{/mnt/etc/config.scm}. Failing to do that, you will have lost your
@ -8536,7 +8538,7 @@ something along these lines:
@example @example
# mkdir /mnt/etc # mkdir /mnt/etc
# cp /etc/configuration/desktop.scm /mnt/etc/config.scm # cp /etc/configuration/desktop.scm /mnt/etc/config.scm
# zile /mnt/etc/config.scm # nano /mnt/etc/config.scm
@end example @end example
You should pay attention to what your configuration file contains, and You should pay attention to what your configuration file contains, and