Changeset cce4232 for chapter08/kernel-inst.xml

Timestamp:

01/15/2003 06:50:48 AM (21 years ago)

Author:

Timothy Bauscher <timothy@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

984ab5a

Parents:

5d0e2ab

Message:

Increased verbosity of command explanations for kernel install.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2327 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

• chapter08/kernel-inst.xml (modified) (2 diffs)

chapter08/kernel-inst.xml

@@ -4 +4 @@
 <title>Installation of the kernel</title>
 
-<para>Building the kernel involves a few steps: configuring it and compiling
-it. There are a few ways to configure the kernel. If you don't like the
-way this book does it, read the <filename>README</filename> that comes
-with the kernel source tree, and find out what the other options are.</para>
+<para>Building the kernel involves a few steps: configuration,
+compilation, and installation. If you don't like the way this
+book configures the kernel, view the <filename>README</filename>
+file in the kernel source tree for alternative methods.</para>
 
-<para>Something you could do, is take the <filename>.config</filename>
-file from your host distribution's kernel source tree and copy it to
-<filename class="directory">$LFS/usr/src/linux-&kernel-version;</filename>.
-This way you don't have to configure the entire kernel from scratch and
-can use your current values. If you choose to do this, first run the
-<userinput>make mrproper</userinput> command below, then copy the
-<filename>.config</filename> file over, then run
-<userinput>make menuconfig</userinput> followed by the rest of the commands
-(<userinput>make oldconfig</userinput> may be better in some situations.
-See the <filename>README</filename> file for more details when to use
-<userinput>make oldconfig</userinput>).</para>
+<para>Prepare for compilation by running the following command:</para>
+
+<para><screen><userinput>make mrproper</userinput></screen></para>
+
+<para>This ensures that the kernel tree is absolutely clean. The kernel
+team recommends that this command be issued prior to
+<emphasis>each</emphasis> kernel compilation. You shouldn't rely
+on the source tree being clean after untarring.</para>
+
+<para>Configure the kernel via a menu-driven interface:</para>
+
+<para><screen><userinput>make menuconfig</userinput></screen></para>
+
+<para><userinput>make oldconfig</userinput> may be more appropriate
+in some situations. See the <filename>README</filename> file for
+more information.</para>
+
+<para>If you wish, you may skip kernel configuration by copying the
+kernel config file, <filename>.config</filename>, from your host
+system to the
+<filename class="directory">$LFS/usr/src/linux-&kernel-version;</filename>
+directory.</para>
+
+<para>Verify dependencies and create dependency information files:</para>
+
+<para><screen><userinput>make dep</userinput></screen></para>
+
+<para>Compile the kernel image:</para>
+
+<para><screen><userinput>make bzImage</userinput></screen></para>
+
+<para>Compile the drivers which have been configured as modules:</para>
+
+<para><screen><userinput>make modules</userinput></screen></para>
 
 <para>If you intend to use kernel modules, you will need an
@@ -30 +53 @@
 interest to you.</para>
 
-<para>Prepare for compilation by running the following command:</para>
+<para>Install the modules:</para>
 
-<para><screen><userinput>make mrproper</userinput></screen></para>
+<para><screen><userinput>make modules_install</userinput></screen></para>
 
-<para>This ensures that the kernel tree is absolutely clean. The kernel
-team recommends that this command be issued prior to
-<emphasis>each</emphasis> kernel compilation. You shouldn't rely
-on the source tree being clean after untarring.</para>
+<para>Kernel compilation has finished, but some of the files created
+still reside in the source tree. To complete the installation, two
+files should to be copied to the <filename>/boot</filename>
+directory.</para>
 
-<para><screen><userinput>make menuconfig &amp;&amp;
-make dep &amp;&amp;
-make bzImage &amp;&amp;
-make modules &amp;&amp;
-make modules_install</userinput></screen></para>
+<para>The path to the kernel file may vary depending on the platform
+you're using. Issue the following command to install the kernel:</para>
 
-<para>Kernel compilation has finished, but the files created are still
-in the source tree. The path to the kernel file,
-<filename>arch/i386/boot/bzImage</filename> below, may vary depending
-on the platform you're using.</para>
+<para><screen><userinput>cp arch/i386/boot/bzImage /boot/lfskernel</userinput></screen></para>
 
-<para><screen><userinput>cp arch/i386/boot/bzImage /boot/lfskernel &amp;&amp;
-cp System.map /boot</userinput></screen></para>
+<para><filename>System.map</filename> is a symbol file for the kernel.
+It maps the function entrypoints of every function in the kernel API,
+as well as the addresses of the kernel data structures for the running
+kernel. Issue the following command to install the map file:</para>
+
+<para><screen><userinput>cp System.map /boot</userinput></screen></para>
 
 </sect2>