[system-administrators-guide/21] Update kernel versions to suit Fed21
stephenw
stephenw at fedoraproject.org
Thu Jan 15 21:25:39 UTC 2015
commit 531f774d3eb2ec26043650ab3875b44c2410dc2b
Author: Stephen Wadeley <swadeley at redhat.com>
Date: Wed Jan 7 23:37:55 2015 +0100
Update kernel versions to suit Fed21
en-US/Manually_Upgrading_the_Kernel.xml | 82 +++++++++++++++---------------
1 files changed, 41 insertions(+), 41 deletions(-)
---
diff --git a/en-US/Manually_Upgrading_the_Kernel.xml b/en-US/Manually_Upgrading_the_Kernel.xml
index c1cfed1..713015e 100644
--- a/en-US/Manually_Upgrading_the_Kernel.xml
+++ b/en-US/Manually_Upgrading_the_Kernel.xml
@@ -239,15 +239,17 @@
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 might differ:
</para>
<screen>~]# <command>yum list installed "kernel-*"</command>
-Loaded plugins: langpacks, refresh-packagekit
+Loaded plugins: langpacks
Installed Packages
-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>
+kernel.x86_64 3.17.4-302.fc21 @updates
+kernel.x86_64 3.17.6-300.fc21 @updates
+kernel.x86_64 3.17.7-300.fc21 @updates
+kernel-core.x86_64 3.17.4-302.fc21 @updates
+kernel-core.x86_64 3.17.6-300.fc21 @updates
+kernel-core.x86_64 3.17.7-300.fc21 @updates
+kernel-modules.x86_64 3.17.4-302.fc21 @updates
+kernel-modules.x86_64 3.17.6-300.fc21 @updates
+kernel-modules.x86_64 3.17.7-300.fc21 @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>
@@ -382,27 +384,27 @@ kernel-modules-extra.x86_64 3.17.3-200.fc20 @updates<
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
+config-3.17.4-302.fc21.x86_64
+config-3.17.6-300.fc21.x86_64
+config-3.17.7-300.fc21.x86_64
efi
elf-memtest86+-5.01
extlinux
grub2
-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
+initramfs-0-rescue-db90b4e3715b42daa871351439343ca4.img
+initramfs-3.17.4-302.fc21.x86_64.img
+initramfs-3.17.6-300.fc21.x86_64.img
+initramfs-3.17.7-300.fc21.x86_64.img
initrd-plymouth.img
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>
+System.map-3.17.4-302.fc21.x86_64
+System.map-3.17.6-300.fc21.x86_64
+System.map-3.17.7-300.fc21.x86_64
+vmlinuz-0-rescue-db90b4e3715b42daa871351439343ca4
+vmlinuz-3.17.4-302.fc21.x86_64
+vmlinuz-3.17.6-300.fc21.x86_64
+vmlinuz-3.17.7-300.fc21.x86_64</screen>
</example>
<para>
<xref
@@ -415,12 +417,12 @@ vmlinuz-3.17.3-200.fc20.x86_64</screen>
</listitem>
<listitem>
<para>
- the latest kernel is <filename>vmlinuz-3.17.3-200.fc20.x86_64</filename>, and
+ the latest kernel is <filename>vmlinuz-3.17.7-300.fc21.x86_64</filename>, and
</para>
</listitem>
<listitem>
<para>
- an <systemitem class="filesystem">initramfs</systemitem> file matching our kernel version, <filename>initramfs-3.17.3-200.fc20.x86_64.img</filename>, also exists.
+ an <systemitem class="filesystem">initramfs</systemitem> file matching our kernel version, <filename>initramfs-3.17.7-300.fc21.x86_64.img</filename>, also exists.
</para>
</listitem>
</itemizedlist>
@@ -440,7 +442,7 @@ vmlinuz-3.17.3-200.fc20.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.17.3-200.fc20.x86_64.img) without --force</screen>
+F: Will not override existing initramfs (/boot/initramfs-3.17.7-300.fc21.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>
@@ -448,10 +450,10 @@ F: Will not override existing initramfs (/boot/initramfs-3.17.3-200.fc20.x86_64.
<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.17.3-200.fc20.x86_64.img</command>
-Image: /boot/initramfs-3.17.3-200.fc20.x86_64.img: 18M
+ <screen>~]# <command>lsinitrd /boot/initramfs-3.17.7-300.fc21.x86_64.img</command>
+Image: /boot/initramfs-3.17.7-300.fc21.x86_64.img: 18M
========================================================================
-Version: dracut-037-11.git20140402.fc20
+Version: dracut-038-31.git20141204.fc21
<lineannotation>[output truncated]</lineannotation></screen>
<para>
See <command>man dracut</command> and <command>man dracut.conf</command> for more information on options and usage.
@@ -462,10 +464,10 @@ Version: dracut-037-11.git20140402.fc20
Examine the <filename>/boot/grub2/grub.cfg</filename> configuration file to ensure that an <computeroutput><filename>initramfs-<replaceable>kernel_version</replaceable>.img</filename></computeroutput> file exists for the kernel version you are booting. For example:
</para>
<screen>~]# <command>grep initramfs /boot/grub2/grub.cfg</command>
- 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-d54d78fd40ab445a9556279010454c22.img</screen>
+ initrd16 /initramfs-3.17.7-300.fc21.x86_64.img
+ initrd16 /initramfs-3.17.6-300.fc21.x86_64.img
+ initrd16 /initramfs-3.17.4-302.fc21.x86_64.img
+ initrd16 /initramfs-0-rescue-db90b4e3715b42daa871351439343ca4.img</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>
@@ -597,9 +599,9 @@ Version: dracut-037-11.git20140402.fc20
</para>
<synopsis><command>grub2-mkconfig</command> <option>-o</option> <option>/boot/grub2/grub.cfg</option></synopsis>
<para>
- Among various code snippets and directives, the <filename>/boot/grub2/grub.cfg</filename> configuration file contains one or more <literal>menuentry</literal> blocks, each representing a single GRUB 2 boot menu entry. These blocks always start with the <literal>menuentry</literal> keyword followed by a title, list of options, and opening curly bracket, and end with a closing curly bracket. Anything between the opening and closing bracket should be indented. For example, the following is a sample <literal>menuentry</literal> block for Fedora 17 with Linux kernel 3.4.0-1.fc17.x86_64:
+ Among various code snippets and directives, the <filename>/boot/grub2/grub.cfg</filename> configuration file contains one or more <literal>menuentry</literal> blocks, each representing a single GRUB 2 boot menu entry. These blocks always start with the <literal>menuentry</literal> keyword followed by a title, list of options, and opening curly bracket, and end with a closing curly bracket. Anything between the opening and closing bracket should be indented. For example, the following is a sample <literal>menuentry</literal> block for Fedora 21 with Linux kernel 3.17.6-300.fc21.x86_64:
</para>
- <programlisting>menuentry 'Fedora (3.4.0-1.fc17.x86_64)' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-77ba9149-751a-48e0-974f-ad94911734b9' {
+ <programlisting>menuentry 'Fedora (3.17.6-300.fc21.x86_64) 21 (Twenty One)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.17.4-301.fc21.x86_64-advanced-effee860-8d55-4e4a-995e-b4c88f9ac9f0' {
load_video
set gfxpayload=keep
insmod gzio
@@ -607,17 +609,15 @@ Version: dracut-037-11.git20140402.fc20
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
- search --no-floppy --fs-uuid --set=root --hint='hd0,msdos1' 4ea24c68-ab10-47d4-8a6b-b8d3a002acba
+ search --no-floppy --fs-uuid --set=root --hint='hd0,msdos1' f19c92f4-9ead-4207-b46a-723b7a2c51c8
else
- search --no-floppy --fs-uuid --set=root 4ea24c68-ab10-47d4-8a6b-b8d3a002acba
+ search --no-floppy --fs-uuid --set=root f19c92f4-9ead-4207-b46a-723b7a2c51c8
fi
- echo 'Loading Fedora (3.4.0-1.fc17.x86_64)'
- linux /vmlinuz-3.4.0-1.fc17.x86_64 root=/dev/mapper/vg_fedora-lv_root ro rd.md=0 rd.dm=0 SYSFONT=True rd.lvm.lv=vg_fedora/lv_swap KEYTABLE=us rd.lvm.lv=vg_fedora/lv_root rd.luks=0 LANG=en_US.UTF-8 rhgb quiet
- echo 'Loading initial ramdisk ...'
- initrd /initramfs-3.4.0-1.fc17.x86_64.img
+ linux16 /vmlinuz-3.17.6-300.fc21.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8
+ initrd16 /initramfs-3.17.6-300.fc21.x86_64.img
}</programlisting>
<para>
- Each <literal>menuentry</literal> block that represents an installed Linux kernel contains <literal>linux</literal> and <literal>initrd</literal> directives followed by the path to the kernel and the <systemitem class="filesystem">initramfs</systemitem> image respectively. If a separate <filename class="directory">/boot</filename> partition was created, the paths to the kernel and the <systemitem class="filesystem">initramfs</systemitem> image are relative to <filename class="directory">/boot</filename>. In the example above, the <literal>initrd /initramfs-3.4.0-1.fc17.x86_64.img</literal> line means that the <systemitem class="filesystem">initramfs</systemitem> image is actually located at <filename>/boot/initramfs-3.4.0-1.fc17.x86_64.img</filename> when the root file system is mounted, and likewise for the kernel path.
+ Each <literal>menuentry</literal> block that represents an installed Linux kernel contains <literal>linux</literal> and <literal>initrd</literal> directives followed by the path to the kernel and the <systemitem class="filesystem">initramfs</systemitem> image respectively. If a separate <filename class="directory">/boot</filename> partition was created, the paths to the kernel and the <systemitem class="filesystem">initramfs</systemitem> image are relative to <filename class="directory">/boot</filename>. In the example above, the <literal>initrd16 /initramfs-3.17.6-300.fc21.x86_64.img</literal> line means that the <systemitem class="filesystem">initramfs</systemitem> image is actually located at <filename>/boot/initramfs-3.17.6-300.fc21.x86_64.img</filename> when the root file system is mounted, and likewise for the kernel path.
</para>
<para>
The kernel version number as given on the <literal>linux /vmlinuz-<replaceable>kernel_version</replaceable></literal> line must match the version number of the <systemitem class="filesystem">initramfs</systemitem> image given on the <literal>initrd /initramfs-<replaceable>kernel_version</replaceable>.img</literal> line of each <literal>menuentry</literal> block. For more information on how to verify the initial RAM disk image, refer to <xref linkend="procedure-Verifying_the_Initial_RAM_Disk_Image" />.
More information about the docs-commits
mailing list