diff options
| author | Bruce Dubbs <bdubbs@linuxfromscratch.org> | 2017-12-28 03:52:38 +0000 |
|---|---|---|
| committer | Bruce Dubbs <bdubbs@linuxfromscratch.org> | 2017-12-28 03:52:38 +0000 |
| commit | 0d84af1cbb0dc825db3e965d5126e5b08f878067 (patch) | |
| tree | 46feb76bec2b74f6ee78baa2ea65ea70ca6a8941 /chapter08 | |
| parent | 9fde3e965f7c86afb36186ec44167192a74b0d7a (diff) | |
Typos and wording changes
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11343 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter08')
| -rw-r--r-- | chapter08/kernel.xml | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/chapter08/kernel.xml b/chapter08/kernel.xml index 635b67da8..5891511d2 100644 --- a/chapter08/kernel.xml +++ b/chapter08/kernel.xml @@ -72,7 +72,7 @@ configuration to a good state that takes your current system architecture into account.</para> - <para>Be sure to enable or disable following features or the system might + <para>Be sure to enable or disable the following features or the system might not work correctly or boot at all:</para> <screen role="nodump" revision="sysv"> @@ -217,10 +217,10 @@ File systems ---> the <filename class="directory">/boot</filename> directory.</para> <caution> - <para>If the host system has a separate /boot partition, the - files copied below should go there. The easiest way to do that - is to bind /boot on the host to /mnt/lfs/boot before proceeding. - As the root user in the <emphasis>host system</emphasis>:</para> + <para>If the host system has a separate /boot partition, the files copied + below should go there. The easiest way to do that is to bind /boot on the + host (outside chroot) to /mnt/lfs/boot before proceeding. As the root + user in the <emphasis>host system</emphasis>:</para> <screen role="nodump"><userinput>mount --bind /boot /mnt/lfs/boot</userinput></screen> </caution> @@ -231,9 +231,9 @@ File systems ---> the automatic setup of the boot process described in the next section. The following command assumes an x86 architecture:</para> -<screen revision="sysv"><userinput remap="install">cp -v arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen> +<screen revision="sysv"><userinput remap="install">cp -iv arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen> -<screen revision="systemd"><userinput remap="install">cp -v arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&versiond;</userinput></screen> +<screen revision="systemd"><userinput remap="install">cp -iv arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&versiond;</userinput></screen> <para><filename>System.map</filename> is a symbol file for the kernel. It maps the function entry points of every function in the kernel API, @@ -241,7 +241,7 @@ File systems ---> kernel. It is used as a resource when investigating kernel problems. Issue the following command to install the map file:</para> -<screen><userinput remap="install">cp -v System.map /boot/System.map-&linux-version;</userinput></screen> +<screen><userinput remap="install">cp -iv System.map /boot/System.map-&linux-version;</userinput></screen> <para>The kernel configuration file <filename>.config</filename> produced by the <command>make menuconfig</command> step @@ -249,7 +249,7 @@ File systems ---> that was just compiled. It is a good idea to keep this file for future reference:</para> -<screen><userinput remap="install">cp -v .config /boot/config-&linux-version;</userinput></screen> +<screen><userinput remap="install">cp -iv .config /boot/config-&linux-version;</userinput></screen> <para>Install the documentation for the Linux kernel:</para> |