[deployment-guide] Changed all "/boot/" strings to "/boot".
Jaromir Hradilek
jhradile at fedoraproject.org
Wed Oct 12 15:54:58 UTC 2011
commit a006b173c3709605d589118f559c85d14a350089
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Tue Oct 11 18:25:04 2011 +0200
Changed all "/boot/" strings to "/boot".
en-US/Manually_Upgrading_the_Kernel.xml | 20 ++++++++++----------
1 files changed, 10 insertions(+), 10 deletions(-)
---
diff --git a/en-US/Manually_Upgrading_the_Kernel.xml b/en-US/Manually_Upgrading_the_Kernel.xml
index 26e4468..f0e1e84 100644
--- a/en-US/Manually_Upgrading_the_Kernel.xml
+++ b/en-US/Manually_Upgrading_the_Kernel.xml
@@ -384,15 +384,15 @@ kernel-headers.x86_64 2.6.38.6-27.fc15 installed</screen>
On all architectures other than IBM eServer System 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:
+ 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.cfg</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:
+ 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>
+ <screen>~]# <command>ls /boot</command>
config-2.6.38.6-26.fc15.x86_64
config-2.6.38.6-27.fc15.x86_64
efi
@@ -412,7 +412,7 @@ vmlinuz-2.6.38.6-27.fc15.x86_64</screen>
<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 two kernels installed (or, more correctly, two kernel files are present in the <filename class="directory">/boot</filename> directory),
</para>
</listitem>
<listitem>
@@ -427,15 +427,15 @@ vmlinuz-2.6.38.6-27.fc15.x86_64</screen>
</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>
+ <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>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:
+ (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>~]# <command>dracut</command></screen>
<para>
@@ -480,7 +480,7 @@ 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, 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">
@@ -610,12 +610,12 @@ title Fedora (2.6.38.6-26.rc1.fc15.x86_64)
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>.
+ 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>
+ 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" />.
More information about the docs-commits
mailing list