commit ed1ee4e0cf9522d646dfc4f9f5d89b82bdcff352
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Mon Nov 24 10:09:34 2014 +0100
Updates to suit Fedora 20
en-US/Manually_Upgrading_the_Kernel.xml | 83 +++++++++++++++++--------------
1 files changed, 46 insertions(+), 37 deletions(-)
---
diff --git a/en-US/Manually_Upgrading_the_Kernel.xml
b/en-US/Manually_Upgrading_the_Kernel.xml
index d836b85..542bf7d 100644
--- a/en-US/Manually_Upgrading_the_Kernel.xml
+++ b/en-US/Manually_Upgrading_the_Kernel.xml
@@ -257,14 +257,15 @@
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>~]# <command>yum list installed
"kernel-*"</command>
-Loaded plugins: langpacks, presto, refresh-packagekit
+Loaded plugins: langpacks, refresh-packagekit
Installed Packages
-kernel.x86_64 3.1.0-0.rc6.git0.3.fc16 @updates-testing
-kernel.x86_64 3.1.0-0.rc9.git0.0.fc16 @updates-testing
-kernel-doc.x86_64 3.1.0-0.rc6.git0.3.fc16 @updates-testing
-kernel-doc.x86_64 3.1.0-0.rc9.git0.0.fc16 @updates-testing
-kernel-headers.x86_64 3.1.0-0.rc6.git0.3.fc16 @updates-testing
-kernel-headers.x86_64 3.1.0-0.rc9.git0.0.fc16 @updates-testing</screen>
+kernel.x86_64 3.16.7-200.fc20 @updates
+kernel.x86_64 3.17.2-200.fc20 @updates
+kernel.x86_64 3.17.3-200.fc20 @updates
+kernel-doc.noarch 3.17.3-200.fc20 @updates
+kernel-modules-extra.x86_64 3.16.7-200.fc20 @updates
+kernel-modules-extra.x86_64 3.17.2-200.fc20 @updates
+kernel-modules-extra.x86_64 3.17.3-200.fc20
@updates</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. See <xref
linkend="s1-kernel-packages" /> for descriptions of the different packages.
</para>
@@ -395,37 +396,49 @@ kernel-headers.x86_64 3.1.0-0.rc9.git0.0.fc16
@updates-testing</screen
<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>~]# <command>ls /boot</command>
-config-3.1.0-0.rc6.git0.3.fc16.x86_64
-config-3.1.0-0.rc9.git0.0.fc16.x86_64
-elf-memtest86+-4.20
-grub
+ <example
+ id="ex-Ensuring_that_the_kernel_and_initramfs_versions_match">
+ <title>Ensuring that the kernel and initramfs versions
match</title>
+ <screen>~]# <command>ls /boot/</command>
+config-3.16.7-200.fc20.x86_64
+config-3.17.2-200.fc20.x86_64
+config-3.17.3-200.fc20.x86_64
+efi
+elf-memtest86+-5.01
+extlinux
grub2
-initramfs-3.1.0-0.rc6.git0.3.fc16.x86_64.img
-initramfs-3.1.0-0.rc9.git0.0.fc16.x86_64.img
+initramfs-0-rescue-d54d78fd40ab445a9556279010454c22.img
+initramfs-3.16.7-200.fc20.x86_64.img
+initramfs-3.17.2-200.fc20.x86_64.img
+initramfs-3.17.3-200.fc20.x86_64.img
initrd-plymouth.img
-memtest86+-4.20
-System.map-3.1.0-0.rc6.git0.3.fc16.x86_64
-System.map-3.1.0-0.rc9.git0.0.fc16.x86_64
-vmlinuz-3.1.0-0.rc6.git0.3.fc16.x86_64
-vmlinuz-3.1.0-0.rc9.git0.0.fc16.x86_64</screen>
- <para>
- The example above shows that:
- </para>
+lost+found
+memtest86+-5.01
+System.map-3.16.7-200.fc20.x86_64
+System.map-3.17.2-200.fc20.x86_64
+System.map-3.17.3-200.fc20.x86_64
+vmlinuz-0-rescue-d54d78fd40ab445a9556279010454c22
+vmlinuz-3.16.7-200.fc20.x86_64
+vmlinuz-3.17.2-200.fc20.x86_64
+vmlinuz-3.17.3-200.fc20.x86_64</screen>
+ </example>
+ <para>
+ <xref
+ linkend="ex-Ensuring_that_the_kernel_and_initramfs_versions_match"
/> 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),
+ we have three kernels installed (or, more correctly, three kernel files are
present in the <filename class="directory">/boot/</filename>
directory),
</para>
</listitem>
<listitem>
<para>
- the latest kernel is
<filename>vmlinuz-vmlinuz-3.1.0-0.rc9.git0.0.fc16.x86_64</filename>, and
+ the latest kernel is
<filename>vmlinuz-3.17.3-200.fc20.x86_64</filename>, and
</para>
</listitem>
<listitem>
<para>
- an <systemitem
class="filesystem">initramfs</systemitem> file matching our kernel
version, <filename>initramfs-3.1.0-0.rc9.git0.0.fc16.x86_64.img</filename>,
also exists.
+ an <systemitem
class="filesystem">initramfs</systemitem> file matching our kernel
version, <filename>initramfs-3.17.3-200.fc20.x86_64.img</filename>, also
exists.
</para>
</listitem>
</itemizedlist>
@@ -445,7 +458,7 @@ vmlinuz-3.1.0-0.rc9.git0.0.fc16.x86_64</screen>
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>~]# <command>dracut</command>
-F: Will not override existing initramfs
(/boot/initramfs-3.1.0-0.rc9.git0.0.fc16.x86_64.img) without --force</screen>
+F: Will not override existing initramfs (/boot/initramfs-3.17.3-200.fc20.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>, for example:
</para>
@@ -453,16 +466,10 @@ F: Will not override existing initramfs
(/boot/initramfs-3.1.0-0.rc9.git0.0.fc16
<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>~]# <command>lsinitrd
/boot/initramfs-3.1.0-0.rc9.git0.0.fc16.x86_64.img</command>
-/boot/initramfs-3.1.0-0.rc9.git0.0.fc16.x86_64.img: 16M
-========================================================================
-dracut-013-15.fc16
+ <screen>~]# <command>lsinitrd
/boot/initramfs-3.17.3-200.fc20.x86_64.img</command>
+Image: /boot/initramfs-3.17.3-200.fc20.x86_64.img: 18M
========================================================================
-drwxr-xr-x 8 root root 0 Oct 11 20:36 .
-lrwxrwxrwx 1 root root 17 Oct 11 20:36 lib -> run/initramfs/lib
-drwxr-xr-x 2 root root 0 Oct 11 20:36 sys
-drwxr-xr-x 2 root root 0 Oct 11 20:36 proc
-lrwxrwxrwx 1 root root 17 Oct 11 20:36 etc -> run/initramfs/etc
+Version: dracut-037-11.git20140402.fc20
<lineannotation>[output truncated]</lineannotation></screen>
<para>
See <command>man dracut</command> and <command>man
dracut.conf</command> for more information on options and usage.
@@ -473,8 +480,10 @@ lrwxrwxrwx 1 root root 17 Oct 11 20:36 etc ->
run/initramfs/etc
Examine the <filename>/boot/grub2/grub.cfg</filename> configuration
file to ensure that an <computeroutput>initrd
<filename>/<replaceable>path</replaceable>/initramfs-<replaceable>kernel_version</replaceable>.img</filename></computeroutput>
exists for the kernel version you are booting. For example:
</para>
<screen>~]# <command>grep initrd
/boot/grub2/grub.cfg</command>
- initrd /initramfs-3.1.0-0.rc6.git0.3.fc16.x86_64.img
- initrd /initramfs-3.1.0-0.rc9.git0.0.fc16.x86_64.img</screen>
+ initrd /initramfs-3.17.3-200.fc20.x86_64.img
+ initrd /initramfs-3.17.2-200.fc20.x86_64.img
+ initrd /initramfs-3.16.7-200.fc20.x86_64.img
+ initrd /initramfs-0-rescue-d54d78fd40ab445a9556279010454</screen>
<para>
See <xref linkend="s1-kernel-boot-loader" /> for more
information on how to read and update the
<filename>/boot/grub2/grub.cfg</filename> file.
</para>
Show replies by date