bug#77061: [PATCH] update doc/guix-cookbook.texi Update instructions for building a custom kernel.

Message ID 87seml1ux8.fsf@gnu.org
State New
Headers
Series bug#77061: [PATCH] update doc/guix-cookbook.texi Update instructions for building a custom kernel. |

Commit Message

Ludovic Courtès April 6, 2025, 9:49 a.m. UTC
  Hi,

Applied with the changes below, thanks!

Ludo’.
  

Patch

diff --git a/doc/guix-cookbook.texi b/doc/guix-cookbook.texi
index e298eb988a..6296156855 100644
--- a/doc/guix-cookbook.texi
+++ b/doc/guix-cookbook.texi
@@ -1725,11 +1725,11 @@  Customizing the Kernel
 definition, but don't worry, there are other ways to work with what we do have.
 
 There are two ways to create a kernel with a custom kernel configuration.  The
-first is to provide a standard @file{defconfig} to @code{customize-linux} 
-procedure. To produce such file you need to obtain Linux source code, create a
-@file{.config} file (using @code{make menuconfig} command, for example) or 
-provide one you already have. After that you will need to run 
-@code{make savedefconfig} command within the kernel source tree - this will
+first is to provide a standard @file{defconfig} to @code{customize-linux}
+procedure.  To produce such file you need to obtain Linux source code, create a
+@file{.config} file (using @code{make menuconfig} command, for example) or
+provide one you already have.  After that you will need to run
+@code{make savedefconfig} command within the kernel source tree---this will
 produce the @file{defconfig} file which we can be used to build a custom kernel.
 
 Below is a sample kernel package.
@@ -1740,7 +1740,8 @@  Customizing the Kernel
     (inherit (customize-linux
               #:linux linux-libre
               #:defconfig
-              (local-file "defconfig")))))
+              (local-file "defconfig")))
+    (name "my-linux-libre")))
 @end lisp
 
 In the same directory as the file defining @code{my-linux-libre} is a file