[deployment-guide/comm-rel: 67/74] UpgradeKernel: indexed
dsilas
dsilas at fedoraproject.org
Tue Jul 6 21:15:03 UTC 2010
commit 7ec256e6cf4eec55db806ee1d074b0972d29031e
Author: fnadge <fnadge at redhat.com>
Date: Tue Jun 29 14:45:19 2010 +0200
UpgradeKernel: indexed
en-US/Manually_Upgrading_the_Kernel.xml | 82 ++++++++++++++++++++++--------
1 files changed, 60 insertions(+), 22 deletions(-)
---
diff --git a/en-US/Manually_Upgrading_the_Kernel.xml b/en-US/Manually_Upgrading_the_Kernel.xml
index f5a72e1..eae8798 100644
--- a/en-US/Manually_Upgrading_the_Kernel.xml
+++ b/en-US/Manually_Upgrading_the_Kernel.xml
@@ -7,51 +7,82 @@
<indexterm
significance="normal">
<primary>kernel</primary>
- <secondary>upgrading</secondary>
+ <secondary>upgrading the kernel</secondary>
</indexterm>
<para>The &MAJOROS; kernel is custom-built by the &MAJOROS; kernel team to ensure its integrity and compatibility with supported hardware. Before Red Hat releases a kernel, 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 Red Hat Network servers and informs you of packages with available updates, including kernel packages.</para>
+ <para>&MAJOROS; kernels are packaged in the RPM format <indexterm><primary>kernel</primary><secondary>package</secondary></indexterm>
+ <indexterm><primary>kernel</primary><secondary>RPM package</secondary></indexterm>
+ <indexterm><primary>package</primary><secondary>kernel RPM</secondary></indexterm>
+ 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 Red Hat Network servers 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>
<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 <indexterm><primary>kernel</primary><secondary>installing kernel packages</secondary></indexterm>
+ <indexterm><primary>installing the kernel</primary></indexterm> 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>
<warning>
<title>Important</title>
<para>Building a custom kernel is not supported by the Red Hat Global Services Support team, and therefore is not explored in this manual.</para>
</warning>
- <para>For more information on installing kernel packages with <application>Yum</application>, refer to <xref
+ <para>For more information on installing kernel packages<indexterm><primary>kernel</primary><secondary>installing kernel packages</secondary></indexterm> with <application>Yum</application>, refer to <xref
linkend="sec-Updating_Packages"/>. For information on Red Hat Network, refer to <xref
linkend="ch-rhnetwork"/>.</para>
<section
id="s1-kernel-packages">
<title>Overview of Kernel Packages</title>
- <para>&MAJOROS; contains the following kernel packages:</para>
+ <para>&MAJOROS; contains the following kernel packages: <indexterm><primary>kernel</primary><secondary>kernel packages</secondary></indexterm></para>
<itemizedlist>
<listitem>
<para>
- <package>kernel</package> — Contains the kernel for single, multicore and multiprocessor systems.</para>
+ <package>kernel</package> —
+ <indexterm><primary>kernel package</primary><secondary>kernel</secondary><tertiary>for single,multicore and multiprocessor systems</tertiary></indexterm>
+ <indexterm><primary>packages</primary><secondary>kernel</secondary><tertiary>for single,multicore and multiprocessor systems</tertiary></indexterm>
+ Contains the kernel for single, multicore and multiprocessor systems.</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> —
+ <indexterm><primary>kernel package</primary><secondary>kernel-devel</secondary><tertiary>kernel headers and makefiles</tertiary></indexterm>
+ <indexterm><primary>packages</primary><secondary>kernel-devel</secondary><tertiary>kernel headers and makefiles</tertiary></indexterm>
+ Contains the kernel headers and makefiles sufficient to build modules against the <package>kernel</package> package.</para>
</listitem>
<listitem>
<para>
- <package>kernel-doc</package> — Contains 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>
+ <package>kernel-doc</package> —
+ <indexterm><primary>kernel package</primary><secondary>kernel-doc</secondary><tertiary>
+ documentation files</tertiary></indexterm>
+ <indexterm><primary>packages</primary><secondary>kernel-doc</secondary><tertiary>
+ documentation files</tertiary></indexterm>
+ 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> —
+ <indexterm><primary>kernel package</primary><secondary>kernel-headers</secondary><tertiary>
+ C header files files</tertiary></indexterm>
+ <indexterm><primary>packages</primary><secondary>kernel-headers</secondary><tertiary>
+ C header files files</tertiary></indexterm>
+ 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>kernel-firmware</package> — Contains all of the firmware files that are required by various devices to operate.</para>
+ <package>kernel-firmware</package> —
+ <indexterm><primary>kernel package</primary><secondary>kernel-firmware</secondary><tertiary>
+ firmware files</tertiary></indexterm>
+ <indexterm><primary>packages</primary><secondary>kernel-firmware</secondary><tertiary>
+ firmware files</tertiary></indexterm>
+ Contains all of the firmware files that are required by various devices to operate.</para>
</listitem>
<listitem>
<para>
- <package>perf</package> — Technically a documentation instead of kernel package, <package>perf</package> contains supporting documentation for the perf tool shipped in each kernel image subpackage.</para>
+ <package>perf</package> —
+ <package>kernel-firmware</package> —
+ <indexterm><primary>kernel package</primary><secondary>perf</secondary><tertiary>
+ firmware files</tertiary></indexterm>
+ <indexterm><primary>packages</primary><secondary>perf</secondary><tertiary>
+ firmware files</tertiary></indexterm>
+ Technically a documentation instead of kernel package, <package>perf</package> contains supporting documentation for the perf tool shipped in each kernel image subpackage.</para>
</listitem>
</itemizedlist>
<!-- TBD6: ensure the release notes contain kernel-source pkg build instructions -->
@@ -69,7 +100,12 @@
significance="normal">
<primary>boot media</primary>
</indexterm>
- <para>Before upgrading the kernel, it is recommended that you take some precautionary steps. The first step is to make sure 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
+ <indexterm><primary>kernel</primary><secondary>upgrading</secondary><tertiary>preparing</tertiary></indexterm>
+ <indexterm><primary>kernel upgrading</primary><secondary>preparing</secondary></indexterm>
+ , it is recommended that you take some precautionary steps. </para>
+ <para>In the first step, make sure working boot media exists
+ <indexterm><primary>kernel</primary><secondary>upgrading</secondary><tertiary>working boot media</tertiary></indexterm>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
@@ -80,7 +116,7 @@
<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 GB</constant> is required for a distribution DVD image, around <constant>700 MB</constant> for a distribution CD image, or around <constant>10 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 root user:</para>
+ 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 root user:</para>
<procedure>
<step>
<para>Install the <application>SYSLINUX</application> bootloader on the USB storage device:</para>
@@ -182,14 +218,14 @@ kernel-headers.x86_64 2.6.32-17.el6 installed
<primary>kernel</primary>
<secondary>downloading</secondary>
</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<indexterm><primary>kernel</primary><secondary>upgrade kernel available</secondary></indexterm> if an updated kernel is available for the system.</para>
<itemizedlist>
<listitem>
- <para>Security Errata — Refer to <ulink
+ <para>Security Errata — <indexterm><primary>kernel</primary><secondary>upgrade kernel available</secondary><tertiary>Security Errata</tertiary></indexterm>Refer to <ulink
url="http://www.redhat.com/security/updates/"/> for information on security errata, including kernel upgrades that fix security issues.</para>
</listitem>
<listitem>
- <para>Via Red Hat Network — Download and install the kernel RPM packages. Red Hat Network can download the latest kernel, upgrade the kernel on the system, create an initial RAM disk image if needed, and configure the boot loader to boot the new kernel. For more information, refer to <ulink
+ <para>Via Red Hat Network — <indexterm><primary>kernel</primary><secondary>upgrade kernel available</secondary><tertiary>via Red Hat network</tertiary></indexterm>Download and install the kernel RPM packages. Red Hat Network can download the latest kernel, upgrade the kernel on the system, create an initial RAM disk image if needed, and configure the boot loader to boot the new kernel. For more information, refer to <ulink
url="http://www.redhat.com/docs/manuals/RHNetwork/"> http://www.redhat.com/docs/manuals/RHNetwork/</ulink>.</para>
</listitem>
</itemizedlist>
@@ -201,7 +237,7 @@ kernel-headers.x86_64 2.6.32-17.el6 installed
<section
id="s1-kernel-perform-upgrade">
<title>Performing the Upgrade</title>
- <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<indexterm><primary>kernel</primary><secondary>performing kernel upgrade</secondary></indexterm>, it is time to upgrade the existing kernel.</para>
<important>
<title>Important</title>
<para>It is strongly recommended that you keep the old kernel in case there are problems with the new kernel.</para>
@@ -217,7 +253,7 @@ kernel-headers.x86_64 2.6.32-17.el6 installed
<title>Verifying the Initial RAM Disk Image</title>
<!--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>The job of the initial RAM disk image <indexterm><primary>initial RAM disk image</primary><secondary>verifying</secondary></indexterm> 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 <trademark
class="registered">IBM</trademark> <trademark
class="trade">eServer</trademark> <trademark
@@ -310,14 +346,14 @@ drwxr-xr-x 2 root root 0 May 3 22:34 etc/modprobe.d
</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>
- <para>On IBM eSeries 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>
+ <para>On IBM eSeries System i machines <indexterm><primary>initial RAM disk image</primary><secondary>verifying</secondary><tertiary>IBM eServer System i</tertiary></indexterm>, 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">
<title>Verifying the Boot Loader</title>
- <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<indexterm><primary>boot loader</primary><secondary>verifying</secondary></indexterm> 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>
@@ -409,7 +445,7 @@ drwxr-xr-x 2 root root 0 May 3 22:34 etc/modprobe.d
<section
id="s3-kernel-boot-loader-grub">
<title>Configuring the GRUB Boot Loader</title>
- <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>
+ <para>GRUB's configuration file<indexterm><primary>GRUB boot loader</primary><secondary>configuring</secondary></indexterm><indexterm><primary>GRUB boot loader</primary><secondary>configuration file</secondary></indexterm>, <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</computeroutpu
t> 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 same stanza.</para>
<example
id="ex-_boot_grub_grub.conf">
@@ -480,7 +516,9 @@ title Red Hat Enterprise Linux 6 (2.6.32-17.el6.x86_64)
<title>Configuring the <trademark
class="registered">OS/400</trademark> Boot Loader</title>
<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>
+ </filename> file
+ <indexterm><primary>OS/400 boot loader</primary><secondary>configuring</secondary></indexterm>
+ <indexterm><primary>OS/400 boot loader</primary><secondary>configuration file</secondary></indexterm> 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">
More information about the docs-commits
mailing list