r5553 - branches/cross-lfs/BOOK/bootable/ppc

manuel at linuxfromscratch.org manuel at linuxfromscratch.org
Tue May 31 11:45:07 PDT 2005

Author: manuel
Date: 2005-05-31 12:45:06 -0600 (Tue, 31 May 2005)
New Revision: 5553

Tagged bootable/ppc/kernel.xml

Modified: branches/cross-lfs/BOOK/bootable/ppc/kernel.xml
--- branches/cross-lfs/BOOK/bootable/ppc/kernel.xml	2005-05-31 18:29:40 UTC (rev 5552)
+++ branches/cross-lfs/BOOK/bootable/ppc/kernel.xml	2005-05-31 18:45:06 UTC (rev 5553)
@@ -1,5 +1,6 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
   <!ENTITY % general-entities SYSTEM "../../general.ent">
   <!ENTITY % patches-entities SYSTEM "../../patches.ent">
@@ -7,170 +8,57 @@
 <sect1 id="ch-bootable-kernel" role="wrap">
-<?dbhtml filename="kernel.html"?>
+  <?dbhtml filename="kernel.html"?>
-<indexterm zone="ch-bootable-kernel"><primary sortas="a-Linux">Linux</primary></indexterm>
+  <title>Linux-&linux-ppc-version;</title>
-<xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
+  <indexterm zone="ch-bootable-kernel">
+  <primary sortas="a-Linux">Linux</primary>
+  </indexterm>
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-  xpointer="xpointer(/sect1/sect2[@role='package'])"/>
+  xpointer="xpointer(id('package-kernel'))"/>
-<sect2 role="installation">
-<title>Installation of the kernel</title>
+  <sect2 role="installation">
+    <title>Installation of the kernel</title>
-<para>Building the kernel involves a few steps—configuration,
-compilation, and installation. Read the <filename>README</filename>
-file in the kernel source tree for alternate methods to the way this
-book configures the kernel.</para>
+    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
+    href="../x86/kernel.xml"
+    xpointer="xpointer(id('install-kernel')/para[1]/range-to(id('install-kernel')/para[18]))"/>
-<para>Prepare for compilation by running the following command:</para>
-<screen><userinput>make mrproper</userinput></screen>
-<para>This ensures that the kernel tree is absolutely clean. The
-kernel team recommends that this command be issued prior to each
-kernel compilation. Do not rely on the source tree being clean after
-<para>Also, ensure that the kernel does not attempt to pass
-hotplugging events to userspace until userspace specifies that it is
-<screen><userinput>sed -i 's@/sbin/hotplug@/bin/true@' kernel/kmod.c</userinput></screen>
-<para>If, in <xref linkend="ch-scripts-console" role=","/> it was decided to
-compile the keymap into the kernel, issue the command below:</para>
-<screen><userinput>loadkeys -m /usr/share/kbd/keymaps/<replaceable>[path to  keymap]</replaceable> > \
-    drivers/char/defkeymap.c</userinput></screen>
-<para>For example, if using a Dutch keyboard, use
-<para>Configure the kernel via a menu-driven interface:</para>
-<screen><userinput>make menuconfig</userinput></screen>
-<para>Alternatively, <command>make oldconfig</command>
-may be more appropriate in some
-situations. <phrase>This will build a basic system with no modules and 
-ext2 support only.</phrase> See the <filename>README</filename> file for more
-<note><para>When configuring the kernel, be sure to enable the
-<quote>Support for hot-pluggable devices</quote> option under the
-<quote>General Setup</quote> menu. This enables hotplug events that
-are used by <command>udev</command> to populate the <filename
-class="directory">/dev</filename> directory with device
-<para>If desired, skip kernel configuration by copying the kernel
-config file, <filename>.config</filename>, from the host system
-(assuming it is available) to the unpacked <filename
-class="directory">linux-&linux-ppc-version;</filename> directory. However,
-we do not recommend this option. It is often better to explore all the
-configuration menus and create the kernel configuration from
-<para>For POSIX-shared memory support, ensure that the kernel config
-option <quote>Virtual memory file system support</quote> is enabled.
-It resides within the <quote>File systems</quote> menu and is normally
-enabled by default.</para>
-<para>LFS bootscripts make the assumption that either both
-<quote>Support for Host-side USB</quote> and <quote>USB device
-filesystem</quote> have been compiled directly into the kernel, or
-that neither is compiled at all.  Bootscripts will not work properly
-if it is a module (usbcore.ko).</para>
-<note><para>NPTL requires the kernel to be compiled with GCC 3.x, in
-this case &gcc-version;. Compiling with 2.95.x is known to cause failures in
-the glibc test suite, so it is not recommended to compile the kernel
-with gcc 2.95.x.</para></note>
-<para>Compile the kernel image and modules:</para>
-<para>If using kernel modules, an
-<filename>/etc/modprobe.conf</filename> file may be needed.
-Information pertaining to modules and kernel configuration is
-located in the kernel documentation in the <filename
-directory. The <emphasis>modprobe.conf</emphasis> man page may also be
-of interest.</para>
-<para>Be very careful when reading other documentation because it
-usually applies to 2.4.x kernels only. As far as we know, kernel
-configuration issues specific to Hotplug and Udev are not documented.
-The problem is that Udev will create a device node only if Hotplug or
-a user-written script inserts the corresponding module into the
-kernel, and not all modules are detectable by Hotplug. Note that
-statements like the one below in the
-<filename>/etc/modprobe.conf</filename> file do not work with
-<para><screen>alias char-major-XXX some-module</screen></para>
-<para>Because of the complications with Hotplug, Udev, and modules, we
-strongly recommend starting with a completely non-modular kernel
-configuration, especially if this is the first time using Udev.</para>
-<para>Install the modules, if the kernel configuration uses them:</para>
-<screen><userinput>make modules_install</userinput></screen>
-<para>If there are many modules and very little space, consider
-stripping and compressing the modules. For most users, such
-compression is not worth the time, but if the system is pressed for
-space, see <ulink url="http://www.linux-mips.org/archives/linux-mips/2002-04/msg00031.html"/>.</para>
-<para>After kernel compilation is complete, additional steps are
-required to complete the installation. Some files need to be copied to
-the <filename class="directory">/boot</filename> directory.</para>
-<para><!--The path to the kernel image may vary depending on the platform
-being used. -->Issue the following command to install the kernel:</para>
 <screen><userinput>cp vmlinux /boot/lfskernel-&linux-ppc-version;</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,
-as well as the addresses of the kernel data structures for the running
-kernel. Issue the following command to install the map file:</para>
+    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
+    href="../x86/kernel.xml"
+    xpointer="xpointer(id('install-kernel')/para[19])"/>
 <screen><userinput>cp System.map /boot/System.map-&linux-ppc-version;</userinput></screen>
-<para>The kernel configuration file <filename>.config</filename>
-produced by the <command>make menuconfig</command> step
-above contains all the configuration selections for the kernel
-that was just compiled. It is a good idea to keep this file for future
+    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
+    href="../x86/kernel.xml"
+    xpointer="xpointer(id('install-kernel')/para[20])"/>
 <screen><userinput>cp .config /boot/config-&linux-ppc-version;</userinput></screen>
-<para>It is important to note that the files in the kernel source
-directory are not owned by <emphasis>root</emphasis>. Whenever a
-package is unpacked as user <emphasis>root</emphasis> (like we did
-inside chroot), the files have the user and group IDs of whatever
-they were on the packager's computer. This is usually not a problem
-for any other package to be installed because the source tree is
-removed after the installation. However, the Linux source tree is
-often retained for a long time.  Because of this, there is a chance
-that whatever user ID the packager used will be assigned to somebody
-on the machine. That person would then have write access to the kernel
+    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
+    href="../x86/kernel.xml"
+    xpointer="xpointer(id('install-kernel')/para[21])"/>
-<para>If the kernel source tree is going to retained, run
-<command>chown -R 0:0</command> on the <filename
-class="directory">linux-&linux-ppc-version;</filename> directory to ensure
-all files are owned by user <emphasis>root</emphasis>.</para>
+    <para>If the kernel source tree is going to retained, run
+    <command>chown -R 0:0</command> on the <filename
+    class="directory">linux-&linux-ppc-version;</filename> directory to
+    ensure all files are owned by user <systemitem
+    class="username">root</systemitem>.</para>
-<xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
+    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
+    href="../x86/kernel.xml"
+    xpointer="xpointer(id('install-kernel')/warning[1])"/>
+  </sect2>
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-  xpointer="xpointer(/sect1/sect2[@role='content'])"/>
+  xpointer="xpointer(id('contents-kernel'))"/>

Modified: branches/cross-lfs/BOOK/bootable/ppc/yaboot.xml
--- branches/cross-lfs/BOOK/bootable/ppc/yaboot.xml	2005-05-31 18:29:40 UTC (rev 5552)
+++ branches/cross-lfs/BOOK/bootable/ppc/yaboot.xml	2005-05-31 18:45:06 UTC (rev 5553)
@@ -8,7 +8,7 @@
 <sect1 id="ch-bootable-yaboot" arch="ppc">
   <?dbhtml filename="yaboot.html"?>
-  <title>Making the LFS system bootable</title>
+  <title>Making the LFS System Bootable</title>
   <indexterm zone="ch-bootable-yaboot">
     <primary sortas="a-Yaboot">Yaboot</primary>

More information about the lfs-book mailing list