mirror of
https://git.in.rschanz.org/ryan77627/guix.git
synced 2024-12-24 05:18:07 -05:00
doc: cookbook: Fix ‘file system’ spelling.
* doc/guix-cookbook.texi (Getting help, Customizing the Kernel): Fix ‘file system’ spelling.
This commit is contained in:
parent
3786f2969b
commit
e892b9c3dc
1 changed files with 5 additions and 5 deletions
|
@ -1288,7 +1288,7 @@ version or compilation options.
|
|||
@subsection Getting help
|
||||
|
||||
Sadly, some applications can be tough to package. Sometimes they need a patch to
|
||||
work with the non-standard filesystem hierarchy enforced by the store.
|
||||
work with the non-standard file system hierarchy enforced by the store.
|
||||
Sometimes the tests won't run properly. (They can be skipped but this is not
|
||||
recommended.) Other times the resulting package won't be reproducible.
|
||||
|
||||
|
@ -1501,7 +1501,7 @@ custom kernel:
|
|||
@lisp
|
||||
(define %macbook41-full-config
|
||||
(append %macbook41-config-options
|
||||
%filesystems
|
||||
%file-systems
|
||||
%efi-support
|
||||
%emulation
|
||||
(@@@@ (gnu packages linux) %default-extra-linux-options)))
|
||||
|
@ -1517,8 +1517,8 @@ custom kernel:
|
|||
#:extra-options %macbook41-config-options))
|
||||
@end lisp
|
||||
|
||||
In the above example @code{%filesystems} is a collection of flags enabling
|
||||
different filesystem support, @code{%efi-support} enables EFI support and
|
||||
In the above example @code{%file-systems} is a collection of flags enabling
|
||||
different file system support, @code{%efi-support} enables EFI support and
|
||||
@code{%emulation} enables a x86_64-linux machine to act in 32-bit mode also.
|
||||
@code{%default-extra-linux-options} are the ones quoted above, which had to be
|
||||
added in since they were replaced in the @code{extra-options} keyword.
|
||||
|
@ -1582,7 +1582,7 @@ The second way to setup the kernel configuration makes more use of Guix's
|
|||
features and allows you to share configuration segments between different
|
||||
kernels. For example, all machines using EFI to boot have a number of EFI
|
||||
configuration flags that they need. It is likely that all the kernels will
|
||||
share a list of filesystems to support. By using variables it is easier to
|
||||
share a list of file systems to support. By using variables it is easier to
|
||||
see at a glance what features are enabled and to make sure you don't have
|
||||
features in one kernel but missing in another.
|
||||
|
||||
|
|
Loading…
Reference in a new issue