[deployment-guide] Adjusted the "Verifying the Initial RAM Disk Image" section.
Jaromir Hradilek
jhradile at fedoraproject.org
Wed Oct 12 15:55:03 UTC 2011
commit dc9f7ceab59625b32650d82a9b7e4ec87c4e37dc
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Tue Oct 11 19:03:17 2011 +0200
Adjusted the "Verifying the Initial RAM Disk Image" section.
en-US/Manually_Upgrading_the_Kernel.xml | 58 ++++++++++++++++--------------
1 files changed, 31 insertions(+), 27 deletions(-)
---
diff --git a/en-US/Manually_Upgrading_the_Kernel.xml b/en-US/Manually_Upgrading_the_Kernel.xml
index f0e1e84..7cbf54c 100644
--- a/en-US/Manually_Upgrading_the_Kernel.xml
+++ b/en-US/Manually_Upgrading_the_Kernel.xml
@@ -393,19 +393,19 @@ kernel-headers.x86_64 2.6.38.6-27.fc15 installed</screen>
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-2.6.38.6-26.fc15.x86_64
-config-2.6.38.6-27.fc15.x86_64
-efi
-elf-memtest86+-4.10
+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
-initramfs-2.6.38.6-26.fc15.x86_64.img
-initramfs-2.6.38.6-27.fc15.x86_64.img
-lost+found
-memtest86+-4.10
-System.map-2.6.38.6-26.fc15.x86_64
-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>
+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
+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>
@@ -417,19 +417,19 @@ vmlinuz-2.6.38.6-27.fc15.x86_64</screen>
</listitem>
<listitem>
<para>
- the latest kernel is <filename>vmlinuz-2.6.38.6-27.fc15.x86_64</filename>, and
+ the latest kernel is <filename>vmlinuz-vmlinuz-3.1.0-0.rc9.git0.0.fc16.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.
+ 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.
</para>
</listitem>
</itemizedlist>
<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" />.
+ In the <filename class="directory">/boot</filename> directory you may find several <filename>initrd-<replaceable><kernel_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>
@@ -442,24 +442,24 @@ vmlinuz-2.6.38.6-27.fc15.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-2.6.38.6-26.fc15.x86_64.img) without --force</screen>
+F: Will not override existing initramfs (/boot/initramfs-3.1.0-0.rc9.git0.0.fc16.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>:
+ 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>
<screen>~]# <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>
- <screen>~]# <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:
+ <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-009-10.fc15
+dracut-013-15.fc16
========================================================================
-drwxr-xr-x 23 root root 0 May 20 14:45 .
-drwxr-xr-x 2 root root 0 May 20 14:45 bin
--rwxr-xr-x 1 root root 38400 Feb 8 12:46 bin/rmdir
--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
+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
<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.
@@ -467,7 +467,7 @@ drwxr-xr-x 2 root root 0 May 20 14:45 bin
</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.
+ Examine the <filename>grub.cfg</filename> configuration file in the <filename>/boot/grub2/</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>
@@ -480,7 +480,11 @@ drwxr-xr-x 2 root root 0 May 20 14:45 bin
<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).
+ 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, run the following command as <systemitem class="username">root</systemitem> to make sure the <filename>/boot/vmlinitrd-<replaceable>kernel_version</replaceable></filename> file already exists:
+ </para>
+ <screen><command>ls -l /boot</command></screen>
+ <para>
+ The <replaceable>kernel_version</replaceable> should match the version of the kernel just installed.
</para>
</section>
<section id="s1-kernel-boot-loader">
More information about the docs-commits
mailing list