[deployment-guide] Clean-up.

Jaromir Hradilek jhradile at fedoraproject.org
Wed Oct 12 15:54:53 UTC 2011


commit f7d7a93b562e7834d4128b78b0766a1406b1e380
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Tue Oct 11 18:17:00 2011 +0200

    Clean-up.

 en-US/Manually_Upgrading_the_Kernel.xml |  501 ++++++++++++++++++-------------
 1 files changed, 296 insertions(+), 205 deletions(-)
---
diff --git a/en-US/Manually_Upgrading_the_Kernel.xml b/en-US/Manually_Upgrading_the_Kernel.xml
index ab8e388..26e4468 100644
--- a/en-US/Manually_Upgrading_the_Kernel.xml
+++ b/en-US/Manually_Upgrading_the_Kernel.xml
@@ -1,11 +1,9 @@
 <?xml version='1.0'?>
 <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
 ]>
-<chapter
-  id="ch-Manually_Upgrading_the_Kernel">
+<chapter id="ch-Manually_Upgrading_the_Kernel">
   <title>Manually Upgrading the Kernel</title>
-  <indexterm
-    significance="normal">
+  <indexterm>
     <primary>kernel</primary>
     <secondary>upgrading the kernel</secondary>
   </indexterm>
@@ -21,9 +19,15 @@
     <primary>package</primary>
     <secondary>kernel RPM</secondary>
   </indexterm>
-  <para>The &MAJOROS; kernel is custom-built by the &MAJOROS; kernel team to ensure its integrity and compatibility with supported hardware. Before a kernel is released, it must first pass a rigorous set of quality assurance tests.</para>
-  <para>&MAJOROS; kernels are packaged in the RPM format so that they are easy to upgrade and verify using the <application>Yum</application> or <application>PackageKit</application> package managers. <application>PackageKit</application> automatically queries the Yum repositories and informs you of packages with available updates, including kernel packages.</para>
-  <para>This chapter is therefore <emphasis>only</emphasis> useful for users who need to manually update a kernel package using the <command>rpm</command> command instead of <command>yum</command>.</para>
+  <para>
+    The &MAJOROS; kernel is custom-built by the &MAJOROS; kernel team to ensure its integrity and compatibility with supported hardware. Before a kernel is released, it must first pass a rigorous set of quality assurance tests.
+  </para>
+  <para>
+    &MAJOROS; kernels are packaged in the RPM format so that they are easy to upgrade and verify using the <application>Yum</application> or <application>PackageKit</application> package managers. <application>PackageKit</application> automatically queries the Yum repositories and informs you of packages with available updates, including kernel packages.
+  </para>
+  <para>
+    This chapter is therefore <emphasis>only</emphasis> useful for users who need to manually update a kernel package using the <command>rpm</command> command instead of <command>yum</command>.
+  </para>
   <indexterm>
     <primary>kernel</primary>
     <secondary>installing kernel packages</secondary>
@@ -33,16 +37,18 @@
   </indexterm>
   <warning>
     <title>Use Yum to install kernels whenever possible</title>
-    <para>Whenever possible, use either the <application>Yum</application> or <application>PackageKit</application> package manager to install a new kernel because they always <emphasis>install</emphasis> a new kernel instead of replacing the current one, which could potentially leave your system unable to boot.</para>
+    <para>
+      Whenever possible, use either the <application>Yum</application> or <application>PackageKit</application> package manager to install a new kernel because they always <emphasis>install</emphasis> a new kernel instead of replacing the current one, which could potentially leave your system unable to boot.
+    </para>
   </warning>
   <indexterm>
     <primary>kernel</primary>
     <secondary>installing kernel packages</secondary>
   </indexterm>
-  <para>For more information on installing kernel packages with <application>Yum</application>, refer to <xref
-      linkend="sec-Updating_Packages"/>.</para>
-  <section
-    id="s1-kernel-packages">
+  <para>
+    For more information on installing kernel packages with <application>Yum</application>, refer to <xref linkend="sec-Updating_Packages" />.
+  </para>
+  <section id="s1-kernel-packages">
     <title>Overview of Kernel Packages</title>
     <indexterm>
       <primary>kernel</primary>
@@ -71,38 +77,32 @@
     <indexterm>
       <primary>kernel package</primary>
       <secondary>kernel-doc</secondary>
-      <tertiary>
-          documentation files</tertiary>
+      <tertiary>documentation files</tertiary>
     </indexterm>
     <indexterm>
       <primary>packages</primary>
       <secondary>kernel-doc</secondary>
-      <tertiary>
-          documentation files</tertiary>
+      <tertiary>documentation files</tertiary>
     </indexterm>
     <indexterm>
       <primary>kernel package</primary>
       <secondary>kernel-headers</secondary>
-      <tertiary>
-          C header files files</tertiary>
+      <tertiary>C header files files</tertiary>
     </indexterm>
     <indexterm>
       <primary>packages</primary>
       <secondary>kernel-headers</secondary>
-      <tertiary>
-          C header files files</tertiary>
+      <tertiary>C header files files</tertiary>
     </indexterm>
     <indexterm>
       <primary>kernel package</primary>
       <secondary>linux-firmware</secondary>
-      <tertiary>
-          firmware files</tertiary>
+      <tertiary>firmware files</tertiary>
     </indexterm>
     <indexterm>
       <primary>packages</primary>
       <secondary>linux-firmware</secondary>
-      <tertiary>
-          firmware files</tertiary>
+      <tertiary>firmware files</tertiary>
     </indexterm>
     <indexterm>
       <primary>kernel package</primary>
@@ -112,51 +112,60 @@
     <indexterm>
       <primary>packages</primary>
       <secondary>perf</secondary>
-      <tertiary>
-          firmware files</tertiary>
+      <tertiary>firmware files</tertiary>
     </indexterm>
-    <para>&MAJOROS; contains the following kernel packages:</para>
+    <para>
+      &MAJOROS; contains the following kernel packages:
+    </para>
     <itemizedlist>
       <listitem>
         <para>
-          <package>kernel</package> — Contains the kernel for single, multicore and multiprocessor systems.</para>
+          <package>kernel</package> — Contains the kernel for single, multicore and multiprocessor systems.
+        </para>
       </listitem>
       <listitem>
         <para>
-          <package>kernel-debug</package> — Contains a kernel with numerous debugging options enabled for kernel diagnosis, at the expense of reduced performance.</para>
+          <package>kernel-debug</package> — Contains a kernel with numerous debugging options enabled for kernel diagnosis, at the expense of reduced performance.
+        </para>
       </listitem>
       <listitem>
         <para>
-          <package>kernel-devel</package> — Contains the kernel headers and makefiles sufficient to build modules against the <package>kernel</package> package.</para>
+          <package>kernel-devel</package> — Contains the kernel headers and makefiles sufficient to build modules against the <package>kernel</package> package.
+        </para>
       </listitem>
       <listitem>
         <para>
-          <package>kernel-debug-devel</package> — Contains the development version of the kernel with numerous debugging options enabled for kernel diagnosis, at the expense of reduced performance.</para>
+          <package>kernel-debug-devel</package> — Contains the development version of the kernel with numerous debugging options enabled for kernel diagnosis, at the expense of reduced performance.
+        </para>
       </listitem>
       <listitem>
         <para>
-          <package>kernel-doc</package> — Documentation files from the kernel source. Various portions of the Linux kernel and the device drivers shipped with it are documented in these files. Installation of this package provides a reference to the options that can be passed to Linux kernel modules at load time.</para>
-        <para>By default, these files are placed in the <filename>/usr/share/doc/kernel-doc-<replaceable>kernel_version</replaceable>/</filename> directory.</para>
+          <package>kernel-doc</package> — Documentation files from the kernel source. Various portions of the Linux kernel and the device drivers shipped with it are documented in these files. Installation of this package provides a reference to the options that can be passed to Linux kernel modules at load time.
+        </para>
+        <para>
+          By default, these files are placed in the <filename>/usr/share/doc/kernel-doc-<replaceable>kernel_version</replaceable>/</filename> directory.
+        </para>
       </listitem>
       <listitem>
         <para>
-          <package>kernel-headers</package> — Includes the C header files that specify the interface between the Linux kernel and user-space libraries and programs. The header files define structures and constants that are needed for building most standard programs.</para>
+          <package>kernel-headers</package> — Includes the C header files that specify the interface between the Linux kernel and user-space libraries and programs. The header files define structures and constants that are needed for building most standard programs.
+        </para>
       </listitem>
       <listitem>
         <para>
-          <package>linux-firmware</package> — Contains all of the firmware files that are required by various devices to operate.</para>
+          <package>linux-firmware</package> — Contains all of the firmware files that are required by various devices to operate.
+        </para>
       </listitem>
       <listitem>
         <para>
-          <package>perf</package> — This package contains supporting scripts and documentation for the <application>perf</application> tool shipped in each kernel image subpackage.</para>
+          <package>perf</package> — This package contains supporting scripts and documentation for the <application>perf</application> tool shipped in each kernel image subpackage.
+        </para>
       </listitem>
     </itemizedlist>
   </section>
-  <section
-    id="s1-kernel-preparing">
+  <section id="s1-kernel-preparing">
     <title>Preparing to Upgrade</title>
-    <indexterm
-      significance="normal">
+    <indexterm>
       <primary>boot media</primary>
     </indexterm>
     <indexterm>
@@ -173,66 +182,89 @@
       <secondary>upgrading</secondary>
       <tertiary>working boot media</tertiary>
     </indexterm>
-    <para>Before upgrading the kernel, it is recommended that you take some precautionary steps.</para>
-    <para>First, ensure that working boot media exists for the system in case a problem occurs. If the boot loader is not configured properly to boot the new kernel, the system cannot be booted into &MAJOROS; without working boot media.</para>
+    <para>
+      Before upgrading the kernel, it is recommended that you take some precautionary steps.
+    </para>
+    <para>
+      First, ensure that working boot media exists for the system in case a problem occurs. If the boot loader is not configured properly to boot the new kernel, the system cannot be booted into &MAJOROS; without working boot media.
+    </para>
     <!--silas: the following instructions for making (USB) boot media are adapted from the RHEL6 beta Installation Guide, "Alternative Method to Make Minimal USB Boot Media" section-->
-    <para>USB media often comes in the form of flash devices sometimes called <firstterm>pen drives</firstterm>, <firstterm>thumb disks</firstterm>, or <firstterm>keys</firstterm>, or as an externally-connected hard disk device. Almost all media of this type is formatted as a <systemitem class="filesystem">VFAT</systemitem> file system. You can create bootable USB media on media formatted as <systemitem class="filesystem">ext2</systemitem>, <systemitem class="filesystem">ext3</systemitem>, <systemitem class="filesystem">ext4</systemitem>, or <systemitem class="filesystem">VFAT</systemitem>.</para>
-    <para>You can transfer a distribution image file or a minimal boot media image file to USB media. Make sure that sufficient free space is available on the device. Around <constant>4&#160;GB</constant> is required for a distribution DVD image, around <constant>700&#160;MB</constant> for a distribution CD image, or around <constant>10&#160;MB</constant> for a minimal boot media image.</para>
-    <para>You must have a copy of the <filename>boot.iso</filename> file from a &MAJOROS; installation DVD, or installation CD-ROM#1, and you need a USB storage device formatted with the <systemitem
-        class="filesystem">VFAT</systemitem>
- file system and around <constant>16 MB</constant> of free space. The following procedure will not affect existing files on the USB storage device unless they have the same path names as the files that you copy onto it. To create USB boot media, perform the following commands as the <systemitem class="username">root</systemitem> user:</para>
+    <para>
+      USB media often comes in the form of flash devices sometimes called <firstterm>pen drives</firstterm>, <firstterm>thumb disks</firstterm>, or <firstterm>keys</firstterm>, or as an externally-connected hard disk device. Almost all media of this type is formatted as a <systemitem class="filesystem">VFAT</systemitem> file system. You can create bootable USB media on media formatted as <systemitem class="filesystem">ext2</systemitem>, <systemitem class="filesystem">ext3</systemitem>, <systemitem class="filesystem">ext4</systemitem>, or <systemitem class="filesystem">VFAT</systemitem>.
+    </para>
+    <para>
+      You can transfer a distribution image file or a minimal boot media image file to USB media. Make sure that sufficient free space is available on the device. Around <constant>4&#160;GB</constant> is required for a distribution DVD image, around <constant>700&#160;MB</constant> for a distribution CD image, or around <constant>10&#160;MB</constant> for a minimal boot media image.
+    </para>
+    <para>
+      You must have a copy of the <filename>boot.iso</filename> file from a &MAJOROS; installation DVD, or installation CD-ROM#1, and you need a USB storage device formatted with the <systemitem class="filesystem">VFAT</systemitem> file system and around <constant>16 MB</constant> of free space. The following procedure will not affect existing files on the USB storage device unless they have the same path names as the files that you copy onto it. To create USB boot media, perform the following commands as the <systemitem class="username">root</systemitem> user:
+    </para>
     <procedure>
       <step>
-        <para>Install the <application>SYSLINUX</application> bootloader on the USB storage device:</para>
-        <screen><command>syslinux /dev/<replaceable>sdX1</replaceable>
-          </command>
-        </screen>
-        <para>...where <replaceable>sdX</replaceable> is the device name.</para>
+        <para>
+          Install the <application>SYSLINUX</application> bootloader on the USB storage device:
+        </para>
+        <screen><command>syslinux /dev/<replaceable>sdX1</replaceable></command></screen>
+        <para>
+          ...where <replaceable>sdX</replaceable> is the device name.
+        </para>
       </step>
       <step>
-        <para>Create mount points for <filename>boot.iso</filename> and the USB storage device:</para>
-        <screen><command>mkdir /mnt/isoboot /mnt/diskboot</command>
-        </screen>
+        <para>
+          Create mount points for <filename>boot.iso</filename> and the USB storage device:
+        </para>
+        <screen><command>mkdir /mnt/isoboot /mnt/diskboot</command></screen>
       </step>
       <step>
-        <para>Mount <filename>boot.iso</filename>:</para>
-        <screen><command>mount -o loop boot.iso /mnt/isoboot</command>
-        </screen>
+        <para>
+          Mount <filename>boot.iso</filename>:
+        </para>
+        <screen><command>mount -o loop boot.iso /mnt/isoboot</command></screen>
       </step>
       <step>
-        <para>Mount the USB storage device:</para>
-        <screen><command>mount /dev/<replaceable>;sdX1</replaceable> /mnt/diskboot</command>
-        </screen>
+        <para>
+          Mount the USB storage device:
+        </para>
+        <screen><command>mount /dev/<replaceable>;sdX1</replaceable> /mnt/diskboot</command></screen>
       </step>
       <step>
-        <para>Copy the <application>ISOLINUX</application> files from the <filename>boot.iso</filename> to the USB storage device:</para>
-        <screen><command>cp /mnt/isoboot/isolinux/* /mnt/diskboot</command>
-        </screen>
+        <para>
+          Copy the <application>ISOLINUX</application> files from the <filename>boot.iso</filename> to the USB storage device:
+        </para>
+        <screen><command>cp /mnt/isoboot/isolinux/* /mnt/diskboot</command></screen>
       </step>
       <step>
-        <para>Use the <filename>isolinux.cfg</filename> file from <filename>boot.iso</filename> as the <filename>syslinux.cfg</filename> file for the USB device:</para>
-        <screen><command>grep -v local /mnt/isoboot/isolinux/isolinux.cfg &gt; /mnt/diskboot/syslinux.cfg</command>
-        </screen>
+        <para>
+          Use the <filename>isolinux.cfg</filename> file from <filename>boot.iso</filename> as the <filename>syslinux.cfg</filename> file for the USB device:
+        </para>
+        <screen><command>grep -v local /mnt/isoboot/isolinux/isolinux.cfg &gt; /mnt/diskboot/syslinux.cfg</command></screen>
       </step>
       <step>
-        <para>Unmount <filename>boot.iso</filename> and the USB storage device:</para>
-        <screen><command>umount /mnt/isoboot /mnt/diskboot</command>
-        </screen>
+        <para>
+          Unmount <filename>boot.iso</filename> and the USB storage device:
+        </para>
+        <screen><command>umount /mnt/isoboot /mnt/diskboot</command></screen>
       </step>
       <step>
-        <para>You should reboot the machine with the boot media and verify that you are able to boot with it before continuing.</para>
+        <para>
+          You should reboot the machine with the boot media and verify that you are able to boot with it before continuing.
+        </para>
       </step>
     </procedure>
-    <para>Alternatively, on systems with a floppy drive, you can create a boot diskette by installing the <package>mkbootdisk</package> package and running the <command>mkbootdisk</command> command as <systemitem class="username">root</systemitem>. Refer to <command>man mkbootdisk</command> man page after installing the package for usage information.</para>
-    <para>To determine which kernel packages are installed, execute the command <command>yum list installed "kernel-*"</command> at a shell prompt. The output will comprise some or all of the following packages, depending on the system's architecture, and the version numbers may differ:</para>
+    <para>
+      Alternatively, on systems with a floppy drive, you can create a boot diskette by installing the <package>mkbootdisk</package> package and running the <command>mkbootdisk</command> command as <systemitem class="username">root</systemitem>. Refer to <command>man mkbootdisk</command> man page after installing the package for usage information.
+    </para>
+    <para>
+      To determine which kernel packages are installed, execute the command <command>yum list installed "kernel-*"</command> at a shell prompt. The output will comprise some or all of the following packages, depending on the system's architecture, and the version numbers may differ:
+    </para>
     <screen>~]#&#160;<command>yum list installed "kernel-*"</command>
 Loaded plugins: langpacks, presto, refresh-packagekit
 Installed Packages
 kernel.x86_64                   2.6.38.6-27.fc15        installed
 kernel-doc.noarch               2.6.38.6-27.fc15        installed
 kernel-headers.x86_64           2.6.38.6-27.fc15        installed</screen>
-    <para>From the output, determine which packages need to be downloaded for the kernel upgrade. For a single processor system, the only required package is the <package>kernel</package> package. Refer to <xref
-        linkend="s1-kernel-packages"/> for descriptions of the different packages.</para>
+    <para>
+      From the output, determine which packages need to be downloaded for the kernel upgrade. For a single processor system, the only required package is the <package>kernel</package> package. Refer to <xref linkend="s1-kernel-packages" /> for descriptions of the different packages.
+    </para>
     <!-- RHEL6: the following info is probably unnecessary
     <para>In the file name, each kernel package contains the architecture for which the package was built. The format is kernel-<replaceable>&lt;variant&gt;</replaceable>-<replaceable>&lt;version&gt;</replaceable>.<replaceable>&lt;arch&gt;</replaceable>.rpm, where <replaceable>&lt;variant&gt;</replaceable> is one of either <package>PAE</package>, <package>xen</package>, and so forth. The <replaceable>&lt;arch&gt;</replaceable> is one of the following:</para>
     <itemizedlist>
@@ -275,11 +307,9 @@ kernel-headers.x86_64           2.6.38.6-27.fc15        installed</screen>
       </listitem>
     </itemizedlist>-->
   </section>
-  <section
-    id="s1-kernel-download">
+  <section id="s1-kernel-download">
     <title>Downloading the Upgraded Kernel</title>
-    <indexterm
-      significance="normal">
+    <indexterm>
       <primary>kernel</primary>
       <secondary>downloading</secondary>
     </indexterm>
@@ -297,37 +327,49 @@ kernel-headers.x86_64           2.6.38.6-27.fc15        installed</screen>
       <secondary>upgrade kernel available</secondary>
       <tertiary>Security Advisories</tertiary>
     </indexterm>
-    <para>There are several ways to determine if an updated kernel is available for the system.</para>
+    <para>
+      There are several ways to determine if an updated kernel is available for the system.
+    </para>
     <itemizedlist>
       <listitem>
-        <para>Security Advisories — Refer to <ulink url="http://fedoraproject.org/wiki/FSA" /> for information on Security Advisories, including kernel upgrades that fix security issues.</para>
+        <para>
+          Security Advisories — Refer to <ulink url="http://fedoraproject.org/wiki/FSA" /> for information on Security Advisories, including kernel upgrades that fix security issues.
+        </para>
       </listitem>
       <listitem>
-        <para>Via Fedora Update System — Download and install the kernel RPM packages. For more information, refer to <ulink url="http://admin.fedoraproject.org/updates/" />.</para>
+        <para>
+          Via Fedora Update System — Download and install the kernel RPM packages. For more information, refer to <ulink url="http://admin.fedoraproject.org/updates/" />.
+        </para>
       </listitem>
     </itemizedlist>
-    <para>To install the kernel manually, continue to <xref linkend="s1-kernel-perform-upgrade"/>.</para>
+    <para>
+      To install the kernel manually, continue to <xref linkend="s1-kernel-perform-upgrade" />.
+    </para>
   </section>
-  <section
-    id="s1-kernel-perform-upgrade">
+  <section id="s1-kernel-perform-upgrade">
     <title>Performing the Upgrade</title>
     <indexterm>
       <primary>kernel</primary>
       <secondary>performing kernel upgrade</secondary>
     </indexterm>
-    <para>After retrieving all of the necessary packages, it is time to upgrade the existing kernel.</para>
+    <para>
+      After retrieving all of the necessary packages, it is time to upgrade the existing kernel.
+    </para>
     <important>
       <title>Keep the old kernel when performing the upgrade</title>
-      <para>It is strongly recommended that you keep the old kernel in case there are problems with the new kernel.</para>
+      <para>
+        It is strongly recommended that you keep the old kernel in case there are problems with the new kernel.
+      </para>
     </important>
-    <para>At a shell prompt, change to the directory that contains the kernel RPM packages. Use <option>-i</option> argument with the <command>rpm</command> command to keep the old kernel. Do <emphasis>not</emphasis> use the <option>-U</option> option, since it overwrites the currently installed kernel, which creates boot loader problems. For example:</para>
-    <screen><command>rpm -ivh kernel-<replaceable>kernel_version</replaceable>.<replaceable>arch</replaceable>.rpm </command>
-    </screen>
-    <para>The next step is to verify that the initial RAM disk image has been created. Refer to <xref
-        linkend="sec-Verifying_the_Initial_RAM_Disk_Image"/> for details.</para>
+    <para>
+      At a shell prompt, change to the directory that contains the kernel RPM packages. Use <option>-i</option> argument with the <command>rpm</command> command to keep the old kernel. Do <emphasis>not</emphasis> use the <option>-U</option> option, since it overwrites the currently installed kernel, which creates boot loader problems. For example:
+    </para>
+    <screen><command>rpm -ivh kernel-<replaceable>kernel_version</replaceable>.<replaceable>arch</replaceable>.rpm </command></screen>
+    <para>
+      The next step is to verify that the initial RAM disk image has been created. Refer to <xref linkend="sec-Verifying_the_Initial_RAM_Disk_Image" /> for details.
+    </para>
   </section>
-  <section
-    id="sec-Verifying_the_Initial_RAM_Disk_Image">
+  <section id="sec-Verifying_the_Initial_RAM_Disk_Image">
     <title>Verifying the Initial RAM Disk Image</title>
     <indexterm>
       <primary>initial RAM disk image</primary>
@@ -335,20 +377,22 @@ kernel-headers.x86_64           2.6.38.6-27.fc15        installed</screen>
     </indexterm>
 	<!--dracut  creates  an initial image used by the kernel for preloading the block device modules (such as
        IDE, SCSI or RAID) which are needed to access the root filesystem.-->
-    <para>The job of the initial RAM disk image is to preload the block device modules, such as for IDE, SCSI or RAID, so that the root file system, on which those modules normally reside, can then be accessed and mounted. On &MAJOROSVER; systems, whenever a new kernel is installed using either the <application>Yum</application>, <application>PackageKit</application>, or <application>RPM</application> package manager, the <application>Dracut</application> utility is always called by the installation scripts to create an <firstterm>initramfs</firstterm> (initial RAM disk image).</para>
-    <para>On all architectures other than IBM&#160;eServer&#160;System&#160;i (see <xref
-        linkend="bh-Verifying_the_Initial_RAM_Disk_Image_and_Kernel_on_IBM_eServer_System_i"/>), you can create an <systemitem
-        class="filesystem">initramfs</systemitem> by running the <command>dracut</command> command. However, you usually don't need to create an <systemitem
-        class="filesystem">initramfs</systemitem> manually: this step is automatically performed if the kernel and its associated packages are installed or upgraded from RPM packages distributed by &OSORG;.
+    <para>
+      The job of the initial RAM disk image is to preload the block device modules, such as for IDE, SCSI or RAID, so that the root file system, on which those modules normally reside, can then be accessed and mounted. On &MAJOROSVER; systems, whenever a new kernel is installed using either the <application>Yum</application>, <application>PackageKit</application>, or <application>RPM</application> package manager, the <application>Dracut</application> utility is always called by the installation scripts to create an <firstterm>initramfs</firstterm> (initial RAM disk image).
+    </para>
+    <para>
+      On all architectures other than IBM&#160;eServer&#160;System&#160;i (see <xref linkend="bh-Verifying_the_Initial_RAM_Disk_Image_and_Kernel_on_IBM_eServer_System_i" />), you can create an <systemitem class="filesystem">initramfs</systemitem> by running the <command>dracut</command> command. However, you usually don't need to create an <systemitem class="filesystem">initramfs</systemitem> manually: this step is automatically performed if the kernel and its associated packages are installed or upgraded from RPM packages distributed by &OSORG;.
     </para>
-    <para>You can verify that an <systemitem
-        class="filesystem">initramfs</systemitem> corresponding to your current kernel version exists and is specified correctly in the <filename>grub.conf</filename> configuration file by following this procedure:</para>
-    <procedure
-      id="procedure-Verifying_the_Initial_RAM_Disk_Image">
+    <para>
+      You can verify that an <systemitem class="filesystem">initramfs</systemitem> corresponding to your current kernel version exists and is specified correctly in the <filename>grub.conf</filename> configuration file by following this procedure:
+    </para>
+    <procedure id="procedure-Verifying_the_Initial_RAM_Disk_Image">
       <title>Verifying the Initial RAM Disk Image</title>
       <step>
-        <para>As <systemitem class="username">root</systemitem>, list the contents in the <filename>/boot/</filename> directory and find the kernel (<filename>vmlinuz-<replaceable>kernel_version</replaceable></filename>) and <filename>initramfs-<replaceable>kernel_version</replaceable></filename> with the latest (most recent) version number:</para>
-          <screen>~]#&#160;<command>ls /boot/</command>
+        <para>
+          As <systemitem class="username">root</systemitem>, list the contents in the <filename>/boot/</filename> directory and find the kernel (<filename>vmlinuz-<replaceable>kernel_version</replaceable></filename>) and <filename>initramfs-<replaceable>kernel_version</replaceable></filename> with the latest (most recent) version number:
+        </para>
+        <screen>~]#&#160;<command>ls /boot/</command>
 config-2.6.38.6-26.fc15.x86_64
 config-2.6.38.6-27.fc15.x86_64
 efi
@@ -363,35 +407,49 @@ System.map-2.6.38.6-27.fc15.x86_64
 vmlinuz-2.6.38.6-26.fc15.x86_64
 vmlinuz-2.6.38.6-27.fc15.x86_64</screen>
         <para>
-          The example above shows that:</para>
+          The example above shows that:
+        </para>
         <itemizedlist>
           <listitem>
-            <para>we have two kernels installed (or, more correctly, two kernel files are present in the <filename class="directory">/boot/</filename> directory),</para>
+            <para>
+              we have two kernels installed (or, more correctly, two kernel files are present in the <filename class="directory">/boot/</filename> directory),
+            </para>
           </listitem>
           <listitem>
-            <para>the latest kernel is <filename>vmlinuz-2.6.38.6-27.fc15.x86_64</filename>, and</para>
+            <para>
+              the latest kernel is <filename>vmlinuz-2.6.38.6-27.fc15.x86_64</filename>, and
+            </para>
           </listitem>
           <listitem>
-            <para>an <systemitem class="filesystem">initramfs</systemitem> file matching our kernel version, <filename>initramfs-2.6.38.6-27.fc15.x86_64.img</filename>, also exists.</para>
+            <para>
+              an <systemitem class="filesystem">initramfs</systemitem> file matching our kernel version, <filename>initramfs-2.6.38.6-27.fc15.x86_64.img</filename>, also exists.
+            </para>
           </listitem>
         </itemizedlist>
-        <important
-          id="important-initrd_files_in_the__boot_directory_are_not_the_same_as_initramfs_files">
+        <important id="important-initrd_files_in_the__boot_directory_are_not_the_same_as_initramfs_files">
           <title>initrd files in the /boot/ directory are not the same as initramfs files</title>
-          <para>In the <filename class="directory">/boot/</filename> directory you may find several <filename>initrd-<replaceable>version</replaceable>kdump.img</filename> files. These are special files created by the <systemitem class="service">kdump</systemitem> mechanism for kernel debugging purposes, are not used to boot the system, and can safely be ignored. For more information on <systemitem class="service">kdump</systemitem>, refer to <xref linkend="ch-kdump" />.</para>
+          <para>
+            In the <filename class="directory">/boot/</filename> directory you may find several <filename>initrd-<replaceable>version</replaceable>kdump.img</filename> files. These are special files created by the <systemitem class="service">kdump</systemitem> mechanism for kernel debugging purposes, are not used to boot the system, and can safely be ignored. For more information on <systemitem class="service">kdump</systemitem>, refer to <xref linkend="ch-kdump" />.
+          </para>
         </important>
       </step>
-      <step
-        performance="optional">
-        <para>(Optional) If your <filename>initramfs-<replaceable>kernel_version</replaceable>
-          </filename> file does not match the version of the latest kernel in <filename>/boot/</filename>, or, in certain other situations, you may need to generate an <filename>initramfs</filename> file with the <application>Dracut</application> utility. Simply invoking <command>dracut</command> as <systemitem class="username">root</systemitem> without options causes it to generate an <filename>initramfs</filename> file in the <filename>/boot/</filename> directory for the latest kernel present in that directory:</para>
+      <step performance="optional">
+        <para>
+          (Optional) If your <filename>initramfs-<replaceable>kernel_version</replaceable></filename> file does not match the version of the latest kernel in <filename>/boot/</filename>, or, in certain other situations, you may need to generate an <filename>initramfs</filename> file with the <application>Dracut</application> utility. Simply invoking <command>dracut</command> as <systemitem class="username">root</systemitem> without options causes it to generate an <filename>initramfs</filename> file in the <filename>/boot/</filename> directory for the latest kernel present in that directory:
+        </para>
         <screen>~]#&#160;<command>dracut</command></screen>
-        <para>You must use the <option>--force</option> option if you want <command>dracut</command> to overwrite an existing <filename>initramfs</filename> (for example, if your <filename>initramfs</filename> has become corrupt). Otherwise <command>dracut</command> will refuse to overwrite the existing <filename>initramfs</filename> file:</para>
+        <para>
+          You must use the <option>--force</option> option if you want <command>dracut</command> to overwrite an existing <filename>initramfs</filename> (for example, if your <filename>initramfs</filename> has become corrupt). Otherwise <command>dracut</command> will refuse to overwrite the existing <filename>initramfs</filename> file:
+        </para>
         <screen>~]#&#160;<command>dracut</command>
 F: Will not override existing initramfs (/boot/initramfs-2.6.38.6-26.fc15.x86_64.img) without --force</screen>
-        <para>You can create an initramfs in the current directory by calling <command>dracut <replaceable>initramfs_name</replaceable> <replaceable>kernel_version</replaceable></command>:</para>
+        <para>
+          You can create an initramfs in the current directory by calling <command>dracut <replaceable>initramfs_name</replaceable> <replaceable>kernel_version</replaceable></command>:
+        </para>
         <screen>~]#&#160;<command>dracut "initramfs-$(uname -r).img" $(uname -r)</command></screen>
-        <para>If you need to specify specific kernel modules to be preloaded, add the names of those modules (minus any file name suffixes such as <filename>.ko</filename>) inside the parentheses of the <computeroutput>add_dracutmodules="<replaceable>module</replaceable> <optional><replaceable>more_modules</replaceable></optional>"</computeroutput> directive of the <filename>/etc/dracut.conf</filename> configuration file. You can list the file contents of an <filename>initramfs</filename> image file created by dracut by using the <command>lsinitrd <replaceable>initramfs_file</replaceable></command> command:</para>
+        <para>
+          If you need to specify specific kernel modules to be preloaded, add the names of those modules (minus any file name suffixes such as <filename>.ko</filename>) inside the parentheses of the <computeroutput>add_dracutmodules="<replaceable>module</replaceable> <optional><replaceable>more_modules</replaceable></optional>"</computeroutput> directive of the <filename>/etc/dracut.conf</filename> configuration file. You can list the file contents of an <filename>initramfs</filename> image file created by dracut by using the <command>lsinitrd <replaceable>initramfs_file</replaceable></command> command:
+        </para>
         <screen>~]#&#160;<command>lsinitrd /boot/initramfs-2.6.38.6-26.fc15.x86_64.img</command>
 /boot/initramfs-2.6.38.6-26.fc15.x86_64.img:
 ========================================================================
@@ -403,73 +461,85 @@ drwxr-xr-x   2 root     root            0 May 20 14:45 bin
 -rwxr-xr-x   1 root     root       116632 Feb  8 12:46 bin/ls
 -rwxr-xr-x   1 root     root        39568 Feb  8 03:27 bin/setfont
 <lineannotation>[output truncated]</lineannotation></screen>
-        <para>Refer to <command>man dracut</command> and <command>man dracut.conf</command> for more information on options and usage.</para>
+        <para>
+          Refer to <command>man dracut</command> and <command>man dracut.conf</command> for more information on options and usage.
+        </para>
       </step>
       <step>
-        <para>Examine the <filename>grub.conf</filename> configuration file in the <filename>/boot/grub/</filename> directory to ensure that an <computeroutput>initrd <filename>initramfs-<replaceable>kernel_version</replaceable>.img</filename></computeroutput> exists for the kernel version you are booting. Refer to <xref linkend="s1-kernel-boot-loader"/> for more information.</para>
+        <para>
+          Examine the <filename>grub.conf</filename> configuration file in the <filename>/boot/grub/</filename> directory to ensure that an <computeroutput>initrd <filename>initramfs-<replaceable>kernel_version</replaceable>.img</filename></computeroutput> exists for the kernel version you are booting. Refer to <xref linkend="s1-kernel-boot-loader" /> for more information.
+        </para>
       </step>
     </procedure>
-    <bridgehead
-      id="bh-Verifying_the_Initial_RAM_Disk_Image_and_Kernel_on_IBM_eServer_System_i">Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i</bridgehead>
+    <bridgehead id="bh-Verifying_the_Initial_RAM_Disk_Image_and_Kernel_on_IBM_eServer_System_i">
+      Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i
+    </bridgehead>
     <indexterm>
       <primary>initial RAM disk image</primary>
       <secondary>verifying</secondary>
       <tertiary>IBM eServer System i</tertiary>
     </indexterm>
-    <para>On IBM eServer System i machines, the initial RAM disk and kernel files are combined into a single file, which is created with the <command>addRamDisk</command> command. This step is performed automatically if the kernel and its associated packages are installed or upgraded from the RPM packages distributed by &OSORG;; thus, it does not need to be executed manually. To verify that it was created, use the command <command>ls -l /boot/</command> to make sure the <filename>/boot/vmlinitrd-<replaceable>kernel_version</replaceable></filename> file already exists (the <filename><replaceable>kernel_version</replaceable></filename> should match the version of the kernel just installed).</para>
+    <para>
+      On IBM eServer System i machines, the initial RAM disk and kernel files are combined into a single file, which is created with the <command>addRamDisk</command> command. This step is performed automatically if the kernel and its associated packages are installed or upgraded from the RPM packages distributed by &OSORG;; thus, it does not need to be executed manually. To verify that it was created, use the command <command>ls -l /boot/</command> to make sure the <filename>/boot/vmlinitrd-<replaceable>kernel_version</replaceable></filename> file already exists (the <filename><replaceable>kernel_version</replaceable></filename> should match the version of the kernel just installed).
+    </para>
   </section>
-  <section
-    id="s1-kernel-boot-loader">
+  <section id="s1-kernel-boot-loader">
     <title>Verifying the Boot Loader</title>
     <indexterm>
       <primary>boot loader</primary>
       <secondary>verifying</secondary>
     </indexterm>
-    <para>When you install a kernel using <command>rpm</command>, the kernel package creates an entry in the boot loader configuration file for that new kernel. However, <command>rpm</command> does <emphasis>not</emphasis> configure the new kernel to boot as the default kernel. You must do this manually when installing a new kernel with <command>rpm</command>.</para>
+    <para>
+      When you install a kernel using <command>rpm</command>, the kernel package creates an entry in the boot loader configuration file for that new kernel. However, <command>rpm</command> does <emphasis>not</emphasis> configure the new kernel to boot as the default kernel. You must do this manually when installing a new kernel with <command>rpm</command>.
+    </para>
     <!-- TBD6: insert link to Installation Guide -->
-    <para>It is always recommended to double-check the boot loader configuration file after installing a new kernel with <command>rpm</command> to ensure that the configuration is correct. Otherwise, the system may not be able to boot into &MAJOROS; properly. If this happens, boot the system with the boot media created earlier and re-configure the boot loader.</para>
-    <para>In the following table, find your system's architecture to determine the boot loader it uses, and then click on the "Refer to" link to jump to the correct instructions for your system.</para>
-        <!--silas: the following table adapted from the RHEL6 Installation Guide, Grub.xml, "Boot Loaders and System Architecture"-->
-    <table
-      id="tb-grub-arch-loaders">
+    <para>
+      It is always recommended to double-check the boot loader configuration file after installing a new kernel with <command>rpm</command> to ensure that the configuration is correct. Otherwise, the system may not be able to boot into &MAJOROS; properly. If this happens, boot the system with the boot media created earlier and re-configure the boot loader.
+    </para>
+    <para>
+      In the following table, find your system's architecture to determine the boot loader it uses, and then click on the "Refer to" link to jump to the correct instructions for your system.
+    </para>
+    <!--silas: the following table adapted from the RHEL6 Installation Guide, Grub.xml, "Boot Loaders and System Architecture"-->
+    <table id="tb-grub-arch-loaders">
       <title>Boot loaders by architecture</title>
-      <tgroup
-        cols="3">
-        <colspec
-          colnum="1"
-          colname="architecture" />
-        <colspec
-          colnum="2"
-          colname="bootloader" />
-        <colspec
-          colnum="3"
-          colname="refer-to" />
+      <tgroup cols="3">
+        <colspec colnum="1" colname="architecture" colwidth="30*" />
+        <colspec colnum="2" colname="bootloader" colwidth="30*" />
+        <colspec colnum="3" colname="refer-to" colwidth="60*" />
         <thead>
           <row>
-            <entry>Architecture</entry>
-            <entry>Boot Loader</entry>
-            <entry>Refer to</entry>
+            <entry>
+              Architecture
+            </entry>
+            <entry>
+              Boot Loader
+            </entry>
+            <entry>
+              Refer to
+            </entry>
           </row>
         </thead>
         <tbody>
           <row>
-            <entry>x86</entry>
-            <entry>GRUB</entry>
             <entry>
-              <xref
-                linkend="s3-kernel-boot-loader-grub"/>
+              x86
+            </entry>
+            <entry>
+              GRUB
+            </entry>
+            <entry>
+              <xref linkend="s3-kernel-boot-loader-grub" />
             </entry>
           </row>
           <row>
             <entry>
-              AMD&#160;AMD64
-              <emphasis>or</emphasis>
-              Intel 64
+              AMD&#160;AMD64 <emphasis>or</emphasis> Intel 64
             </entry>
-            <entry>GRUB</entry>
             <entry>
-              <xref
-                linkend="s3-kernel-boot-loader-grub"/>
+              GRUB
+            </entry>
+            <entry>
+              <xref linkend="s3-kernel-boot-loader-grub" />
             </entry>
           </row>
           <row>
@@ -480,32 +550,35 @@ drwxr-xr-x   2 root     root            0 May 20 14:45 bin
               OS/400
             </entry>
             <entry>
-              <xref
-                linkend="s2-kernel-boot-loader-iseries"/>
+              <xref linkend="s2-kernel-boot-loader-iseries" />
             </entry>
           </row>
           <row>
             <entry>
               IBM&#160;eServer&#160;System&#160;p
             </entry>
-            <entry>YABOOT</entry>
             <entry>
-              <xref
-                linkend="s2-kernel-boot-loader-pseries"/>
+              YABOOT
+            </entry>
+            <entry>
+              <xref linkend="s2-kernel-boot-loader-pseries" />
             </entry>
           </row>
           <row>
             <entry>
               IBM&#160;System&#160;z
             </entry>
-            <entry>z/IPL</entry>
-            <entry></entry>
+            <entry>
+              z/IPL
+            </entry>
+            <entry>
+              &mdash;
+            </entry>
           </row>
         </tbody>
       </tgroup>
     </table>
-    <section
-      id="s3-kernel-boot-loader-grub">
+    <section id="s3-kernel-boot-loader-grub">
       <title>Configuring the GRUB Boot Loader</title>
       <indexterm>
         <primary>GRUB boot loader</primary>
@@ -515,9 +588,10 @@ drwxr-xr-x   2 root     root            0 May 20 14:45 bin
         <primary>GRUB boot loader</primary>
         <secondary>configuration file</secondary>
       </indexterm>
-      <para>GRUB's configuration file, <filename>/boot/grub/grub.conf</filename>, contains a few lines with directives, such as <computeroutput>default</computeroutput>, <computeroutput>timeout</computeroutput>, <computeroutput>splashimage</computeroutput> and <computeroutput>hiddenmenu</computeroutput> (the last directive has no argument). The remainder of the file contains 4-line <firstterm>stanzas</firstterm> that each refer to an installed kernel. These stanzas always start with a <computeroutput>title</computeroutput> entry, after which the associated <computeroutput>root</computeroutput>, <computeroutput>kernel</computeroutput> and <computeroutput>initrd</computeroutput> directives should always be indented. Ensure that each stanza starts with a <computeroutput>title</computeroutput> that contains a version number (in parentheses) that matches the version number in the <computeroutput>kernel /vmlinuz-<replaceable>version_number</replaceable></computeroutput> line of th
 e same stanza.</para>
-      <example
-        id="ex-_boot_grub_grub.conf">
+      <para>
+        GRUB's configuration file, <filename>/boot/grub/grub.conf</filename>, contains a few lines with directives, such as <computeroutput>default</computeroutput>, <computeroutput>timeout</computeroutput>, <computeroutput>splashimage</computeroutput> and <computeroutput>hiddenmenu</computeroutput> (the last directive has no argument). The remainder of the file contains 4-line <firstterm>stanzas</firstterm> that each refer to an installed kernel. These stanzas always start with a <computeroutput>title</computeroutput> entry, after which the associated <computeroutput>root</computeroutput>, <computeroutput>kernel</computeroutput> and <computeroutput>initrd</computeroutput> directives should always be indented. Ensure that each stanza starts with a <computeroutput>title</computeroutput> that contains a version number (in parentheses) that matches the version number in the <computeroutput>kernel /vmlinuz-<replaceable>version_number</replaceable></computeroutput> line of the sa
 me stanza.
+      </para>
+      <example id="ex-_boot_grub_grub.conf">
         <title>/boot/grub/grub.conf</title>
         <programlisting># grub.conf generated by anaconda
 <lineannotation>[comments omitted]</lineannotation>
@@ -535,34 +609,44 @@ title Fedora (2.6.38.6-26.rc1.fc15.x86_64)
         kernel /boot/vmlinuz-2.6.38.6-26.fc15.x86_64 ro root=UUID=e8148266-4a56-4f4d-b6df-9eafea4586b2 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
         initrd /boot/initramfs-2.6.38.6-26.fc15.x86_64.img</programlisting>
       </example>
-      <para>If a separate <filename>/boot/</filename> partition was created, the paths to the kernel and the <systemitem class="filesystem">initramfs</systemitem> image are relative to <filename>/boot/</filename>. This is the case in <xref linkend="ex-_boot_grub_grub.conf"/>, therefore the <computeroutput>initrd <filename>/initramfs-2.6.38.6-27.fc15.x86_64.img</filename></computeroutput> line in the first kernel stanza means that the <systemitem class="filesystem">initramfs</systemitem> image is actually located at <filename>/boot/initramfs-2.6.38.6-27.fc15.x86_64.img</filename> when the root file system is mounted, and likewise for the kernel path (for example: <computeroutput>kernel <filename>/vmlinuz-2.6.38.6-27.fc15.x86_64</filename></computeroutput>) in each stanza of <filename>grub.conf</filename>.</para>
-      <note
-        id="note-The_initrd_directive_in_grub.conf_refers_to_an_initramfs_image">
+      <para>
+        If a separate <filename>/boot/</filename> partition was created, the paths to the kernel and the <systemitem class="filesystem">initramfs</systemitem> image are relative to <filename>/boot/</filename>. This is the case in <xref linkend="ex-_boot_grub_grub.conf" />, therefore the <computeroutput>initrd <filename>/initramfs-2.6.38.6-27.fc15.x86_64.img</filename></computeroutput> line in the first kernel stanza means that the <systemitem class="filesystem">initramfs</systemitem> image is actually located at <filename>/boot/initramfs-2.6.38.6-27.fc15.x86_64.img</filename> when the root file system is mounted, and likewise for the kernel path (for example: <computeroutput>kernel <filename>/vmlinuz-2.6.38.6-27.fc15.x86_64</filename></computeroutput>) in each stanza of <filename>grub.conf</filename>.
+      </para>
+      <note id="note-The_initrd_directive_in_grub.conf_refers_to_an_initramfs_image">
         <title>The initrd directive in grub.conf refers to an initramfs image</title>
-        <para>In kernel boot stanzas in <filename>grub.conf</filename>, the <computeroutput>initrd</computeroutput> directive must point to the location (relative to the <filename class="directory">/boot/</filename> directory if it is on a separate partition) of the <emphasis><filename>initramfs</filename>
-          </emphasis> file corresponding to the same kernel version. This directive is called <computeroutput>initrd</computeroutput> because the previous tool which created initial RAM disk images, <command>mkinitrd</command>, created what were known as <systemitem
-            class="filesystem">initrd</systemitem> files. Thus the <filename>grub.conf</filename> directive remains <systemitem
-            class="filesystem">initrd</systemitem> to maintain compatibility with other tools. The file-naming convention of systems using the <command>dracut</command> utility to create the initial RAM disk image is: <filename>initramfs-<replaceable>kernel_version</replaceable>.img</filename>
+        <para>
+          In kernel boot stanzas in <filename>grub.conf</filename>, the <computeroutput>initrd</computeroutput> directive must point to the location (relative to the <filename class="directory">/boot/</filename> directory if it is on a separate partition) of the <emphasis><filename>initramfs</filename></emphasis> file corresponding to the same kernel version. This directive is called <computeroutput>initrd</computeroutput> because the previous tool which created initial RAM disk images, <command>mkinitrd</command>, created what were known as <systemitem class="filesystem">initrd</systemitem> files. Thus the <filename>grub.conf</filename> directive remains <systemitem class="filesystem">initrd</systemitem> to maintain compatibility with other tools. The file-naming convention of systems using the <command>dracut</command> utility to create the initial RAM disk image is: <filename>initramfs-<replaceable>kernel_version</replaceable>.img</filename>
         </para>
         <para>
-          <application>Dracut</application> is a new utility available in &MAJOROSVER;, and much-improved over <command>mkinitrd</command>. For information on using <application>Dracut</application>, refer to <xref
-            linkend="sec-Verifying_the_Initial_RAM_Disk_Image"/>.</para>
+          <application>Dracut</application> is a new utility available in &MAJOROSVER;, and much-improved over <command>mkinitrd</command>. For information on using <application>Dracut</application>, refer to <xref linkend="sec-Verifying_the_Initial_RAM_Disk_Image" />.
+        </para>
       </note>
-      <para>You should ensure that the kernel version number as given on the <computeroutput>kernel <filename>/vmlinuz-<replaceable>kernel_version</replaceable></filename></computeroutput> line matches the version number of the <systemitem class="filesystem">initramfs</systemitem> image given on the <computeroutput>initrd <filename>/initramfs-<replaceable>kernel_version</replaceable>.img</filename></computeroutput> line of each stanza. Refer to <xref linkend="procedure-Verifying_the_Initial_RAM_Disk_Image"/> for more information.</para>
-      <para>The <computeroutput>default=</computeroutput> directive tells GRUB which kernel to boot <emphasis>by default</emphasis>. Each <computeroutput>title</computeroutput> in <filename>grub.conf</filename> represents a bootable kernel. GRUB counts the <computeroutput>title</computeroutput>d stanzas representing bootable kernels starting with <constant>0</constant>. In <xref
-          linkend="ex-_boot_grub_grub.conf"/>, the line <computeroutput>default=1</computeroutput> indicates that GRUB will boot, by default, the <emphasis>second</emphasis> kernel entry, i.e. <computeroutput>title Fedora (2.6.38.6-26.fc15.x86_64)</computeroutput>.</para>
-      <para>In <xref linkend="ex-_boot_grub_grub.conf"/> GRUB is therefore configured to boot an older kernel, when we compare by version numbers. In order to boot the newer kernel, which is the <emphasis>first</emphasis>
-        <computeroutput>title</computeroutput> entry in <filename>grub.conf</filename>, we would need to change the <computeroutput>default</computeroutput> value to <constant>0</constant>.</para>
-      <para>After installing a new kernel with <command>rpm</command>, verify that <filename>/boot/grub/grub.conf</filename> is correct, change the <computeroutput>default=</computeroutput> value to the new kernel (while remembering to count from <constant>0</constant>), and reboot the computer into the new kernel. Ensure your hardware is detected by watching the boot process output.</para>
-      <para>If GRUB presents an error and is unable to boot into the default kernel, it is often easiest to try to boot into an alternative or older kernel so that you can fix the problem.</para>
+      <para>
+        You should ensure that the kernel version number as given on the <computeroutput>kernel <filename>/vmlinuz-<replaceable>kernel_version</replaceable></filename></computeroutput> line matches the version number of the <systemitem class="filesystem">initramfs</systemitem> image given on the <computeroutput>initrd <filename>/initramfs-<replaceable>kernel_version</replaceable>.img</filename></computeroutput> line of each stanza. Refer to <xref linkend="procedure-Verifying_the_Initial_RAM_Disk_Image" /> for more information.
+      </para>
+      <para>
+        The <computeroutput>default=</computeroutput> directive tells GRUB which kernel to boot <emphasis>by default</emphasis>. Each <computeroutput>title</computeroutput> in <filename>grub.conf</filename> represents a bootable kernel. GRUB counts the <computeroutput>title</computeroutput>d stanzas representing bootable kernels starting with <constant>0</constant>. In <xref linkend="ex-_boot_grub_grub.conf" />, the line <computeroutput>default=1</computeroutput> indicates that GRUB will boot, by default, the <emphasis>second</emphasis> kernel entry, i.e. <computeroutput>title Fedora (2.6.38.6-26.fc15.x86_64)</computeroutput>.
+      </para>
+      <para>
+        In <xref linkend="ex-_boot_grub_grub.conf" /> GRUB is therefore configured to boot an older kernel, when we compare by version numbers. In order to boot the newer kernel, which is the <emphasis>first</emphasis> <computeroutput>title</computeroutput> entry in <filename>grub.conf</filename>, we would need to change the <computeroutput>default</computeroutput> value to <constant>0</constant>.
+      </para>
+      <para>
+        After installing a new kernel with <command>rpm</command>, verify that <filename>/boot/grub/grub.conf</filename> is correct, change the <computeroutput>default=</computeroutput> value to the new kernel (while remembering to count from <constant>0</constant>), and reboot the computer into the new kernel. Ensure your hardware is detected by watching the boot process output.
+      </para>
+      <para>
+        If GRUB presents an error and is unable to boot into the default kernel, it is often easiest to try to boot into an alternative or older kernel so that you can fix the problem.
+      </para>
       <important>
         <title>Causing the GRUB boot menu to display</title>
-        <para>If you set the <computeroutput>timeout</computeroutput> directive in <filename>grub.conf</filename> to <constant>0</constant>, GRUB will not display its list of bootable kernels when the system starts up. In order to display this list when booting, press and hold any alphanumeric key while and immediately after BIOS information is displayed, and GRUB will present you with the GRUB menu.</para>
+        <para>
+          If you set the <computeroutput>timeout</computeroutput> directive in <filename>grub.conf</filename> to <constant>0</constant>, GRUB will not display its list of bootable kernels when the system starts up. In order to display this list when booting, press and hold any alphanumeric key while and immediately after BIOS information is displayed, and GRUB will present you with the GRUB menu.
+        </para>
       </important>
-      <para>Alternatively, use the boot media you created earlier to boot the system.</para>
+      <para>
+        Alternatively, use the boot media you created earlier to boot the system.
+      </para>
     </section>
-    <section
-      id="s2-kernel-boot-loader-iseries">
+    <section id="s2-kernel-boot-loader-iseries">
       <title>Configuring the OS/400 Boot Loader</title>
       <indexterm>
         <primary>OS/400 boot loader</primary>
@@ -572,28 +656,31 @@ title Fedora (2.6.38.6-26.rc1.fc15.x86_64)
         <primary>OS/400 boot loader</primary>
         <secondary>configuration file</secondary>
       </indexterm>
-      <para>The <filename>/boot/vmlinitrd-<replaceable>kernel-version</replaceable>
-        </filename> file is installed when you upgrade the kernel. However, you must use the <command>dd</command> command to configure the system to boot the new kernel.</para>
-      <orderedlist
-        continuation="restarts"
-        inheritnum="ignore">
+      <para>
+        The <filename>/boot/vmlinitrd-<replaceable>kernel-version</replaceable></filename> file is installed when you upgrade the kernel. However, you must use the <command>dd</command> command to configure the system to boot the new kernel.
+      </para>
+      <orderedlist continuation="restarts" inheritnum="ignore">
         <listitem>
-          <para>As <systemitem class="username">root</systemitem>, issue the command <command>cat /proc/iSeries/mf/side</command> to determine the default side (either A, B, or C).</para>
+          <para>
+            As <systemitem class="username">root</systemitem>, issue the command <command>cat /proc/iSeries/mf/side</command> to determine the default side (either A, B, or C).
+          </para>
         </listitem>
         <listitem>
-          <para>As <systemitem class="username">root</systemitem>, issue the following command, where <replaceable>kernel-version</replaceable> is the version of the new kernel and <replaceable>side</replaceable> is the side from the previous command:</para>
-          <screen>
-<command>dd if=/boot/vmlinitrd-<replaceable>kernel-version</replaceable> of=/proc/iSeries/mf/<replaceable>side</replaceable>/vmlinux bs=8k</command>
-          </screen>
+          <para>
+            As <systemitem class="username">root</systemitem>, issue the following command, where <replaceable>kernel-version</replaceable> is the version of the new kernel and <replaceable>side</replaceable> is the side from the previous command:
+          </para>
+          <screen><command>dd if=/boot/vmlinitrd-<replaceable>kernel-version</replaceable> of=/proc/iSeries/mf/<replaceable>side</replaceable>/vmlinux bs=8k</command></screen>
         </listitem>
       </orderedlist>
-      <para>Begin testing the new kernel by rebooting the computer and watching the messages to ensure that the hardware is detected properly.</para>
+      <para>
+        Begin testing the new kernel by rebooting the computer and watching the messages to ensure that the hardware is detected properly.
+      </para>
     </section>
-    <section
-      id="s2-kernel-boot-loader-pseries">
+    <section id="s2-kernel-boot-loader-pseries">
       <title>Configuring the YABOOT Boot Loader</title>
-      <para>IBM eServer System p uses YABOOT as its boot loader. YABOOT uses <filename>/etc/aboot.conf</filename> as its configuration file. Confirm that the file contains an <computeroutput>image</computeroutput> section with the same version as the <package>kernel</package> package just installed, and likewise for the <systemitem
-          class="filesystem">initramfs</systemitem> image:</para>
+      <para>
+        IBM eServer System p uses YABOOT as its boot loader. YABOOT uses <filename>/etc/aboot.conf</filename> as its configuration file. Confirm that the file contains an <computeroutput>image</computeroutput> section with the same version as the <package>kernel</package> package just installed, and likewise for the <systemitem class="filesystem">initramfs</systemitem> image:
+      </para>
       <screen>boot=/dev/sda1 init-message=Welcome to &MAJOROS;! Hit &lt;TAB&gt; for boot options
 partition=2 timeout=30 install=/usr/lib/yaboot/yaboot delay=10 nonvram
 image=/vmlinuz-2.6.32-17.EL
@@ -606,8 +693,12 @@ image=/vmlinuz-2.6.32-19.EL
 	 read-only
 	 initrd=/initramfs-2.6.32-19.EL.img
 	 append="root=LABEL=/"</screen>
-      <para>Notice that the default is not set to the new kernel. The kernel in the first image is booted by default. To change the default kernel to boot either move its image stanza so that it is the first one listed or add the directive <computeroutput>default</computeroutput> and set it to the <computeroutput>label</computeroutput> of the image stanza that contains the new kernel.</para>
-      <para>Begin testing the new kernel by rebooting the computer and watching the messages to ensure that the hardware is detected properly.</para>
+      <para>
+        Notice that the default is not set to the new kernel. The kernel in the first image is booted by default. To change the default kernel to boot either move its image stanza so that it is the first one listed or add the directive <computeroutput>default</computeroutput> and set it to the <computeroutput>label</computeroutput> of the image stanza that contains the new kernel.
+      </para>
+      <para>
+        Begin testing the new kernel by rebooting the computer and watching the messages to ensure that the hardware is detected properly.
+      </para>
     </section>
   </section>
 </chapter>


More information about the docs-commits mailing list