commit 422ba83fcac14e6b9edc8fd1538b4185687d2d84
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Fri Aug 14 14:03:04 2015 +0200
Introduction to GRUB 2
Rewritten and with new title.
en-US/Working_with_the_GRUB_2_Boot_Loader.xml | 31 ++++++------------------
1 files changed, 8 insertions(+), 23 deletions(-)
---
diff --git a/en-US/Working_with_the_GRUB_2_Boot_Loader.xml
b/en-US/Working_with_the_GRUB_2_Boot_Loader.xml
index b0b37b2..8d50d44 100644
--- a/en-US/Working_with_the_GRUB_2_Boot_Loader.xml
+++ b/en-US/Working_with_the_GRUB_2_Boot_Loader.xml
@@ -24,38 +24,23 @@
&MAJOROSVER; is distributed with the GNU GRand Unified Boot loader (GRUB) version 2
boot loader, which allows the user to select an operating system or kernel to be loaded at
system boot time. GRUB 2 also allows the user to pass arguments to the kernel.
</para>
- <section id="sec-Configuring_the_GRUB_2_Boot_Loader">
- <title>Configuring the GRUB 2 Boot Loader</title>
+<section id="sec-Introduction_to_GRUB_2">
+ <title>Introduction to GRUB 2</title>
+
<para>
GRUB 2 reads its configuration from the
<filename>/boot/grub2/grub.cfg</filename> file on traditional BIOS-based
machines and from the <filename>/boot/efi/EFI/redhat/grub.cfg</filename> file
on UEFI machines. This file contains menu information.
</para>
<para>
- The <filename>grub.cfg</filename> is not supposed to be edited as it
is generated by the <application>/usr/sbin/grub2-mkconfig</application>
utility based on Linux kernels located in the <filename
class="directory">/boot/</filename> directory, template files located
in <filename class="directory">/etc/grub.d/</filename>, and custom
settings in the <filename>/etc/default/grub</filename> file. Any manual edits
could therefore be lost during updates. The GRUB 2 configuration file,
<filename>grub.cfg</filename>, is automatically updated each time a new kernel
is installed. Note that any manual changes to
<filename>/etc/default/grub</filename> require rebuilding the
<filename>grub.cfg</filename> file.</para>
+ The GRUB 2 configuration file, <filename>grub.cfg</filename>, is
generated by the <application>/usr/sbin/grub2-mkconfig</application> utility
based on Linux kernels located in the <filename
class="directory">/boot/</filename> directory, template files located
in <filename class="directory">/etc/grub.d/</filename>, and custom
settings in the <filename>/etc/default/grub</filename> file. The file is not
supposed to be edited as any edits to the file could be lost during updates. The file is
automatically updated each time a new kernel is installed.</para>
<para>
-The <filename>/etc/default/grub</filename> file is used by
<command>grub2-mkconfig</command>, which should only be used by
<systemitem>anaconda</systemitem> when creating
<filename>grub.cfg</filename> initially during the installation process, and
can be used in the event of a system failure, for example if the boot loader
configurations need to be recreated from scratch. In general it is not recommended to use
<filename>grub2-mkconfig</filename> manually except as a last resort. Normal
operations on <filename>grub.cfg</filename>, such as the removal and addition
of new kernels, should be done with the <command>grubby</command> tool and,
for scripts, using <command>new-kernel-pkg</command> tool. If you use
<command>grubby</command> to modify the default kernel the changes continues
to be inherited when new kernels are installed.
+ Normal operations on <filename>grub.cfg</filename>, such as the
removal and addition of new kernels, should be done using the
<command>grubby</command> tool and, for scripts, using
<command>new-kernel-pkg</command> tool. If you use
<command>grubby</command> to modify the default kernel the changes will be
inherited when new kernels are installed. For more information on
<command>grubby</command>, see <xref
linkend="sec-Configuring_GRUB_2_Using_the_grubby_Tool" />.
</para>
-
- <bridgehead renderas="sect3">Rebuilding the GRUB 2 Configuration
File</bridgehead>
<para>
- To rebuild the GRUB 2 configuration file manually using the
<command>grub2-mkconfig</command> command, proceed as follows:
- </para>
+The <filename>/etc/default/grub</filename> file is used by the
<command>grub2-mkconfig</command> tool, which is used by
<systemitem>anaconda</systemitem> when creating
<filename>grub.cfg</filename> during the installation process, and can be used
in the event of a system failure, for example if the boot loader configurations need to be
recreated. In general it is not recommended to use
<filename>grub2-mkconfig</filename> manually except as a last resort. Note
that any manual changes to <filename>/etc/default/grub</filename> require
rebuilding the <filename>grub.cfg</filename> file.
+</para>
- <itemizedlist>
- <listitem>
- <para>
- On BIOS-based machines, issue the following command as
<systemitem class="username">root</systemitem>:
- <screen>~]# <command>grub2-mkconfig -o
/boot/grub2/grub.cfg</command></screen>
- </para>
- </listitem>
- <listitem>
- <para>
- On UEFI-based machines, issue the following command as
<systemitem class="username">root</systemitem>:
- <screen>~]# <command>grub2-mkconfig -o
/boot/efi/EFI/redhat/grub.cfg</command></screen>
- </para>
- </listitem>
- </itemizedlist>
-<bridgehead renderas="sect3">Menu Entries in grub.cfg</bridgehead>
+<bridgehead id="bh-Menu_Entries_in_grub.cfg"
renderas="sect3">Menu Entries in grub.cfg</bridgehead>
<para>
Among various code snippets and directives, the
<filename>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 an 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 &MAJOROSVER; with Linux kernel 3.17.4-301.fc21.x86_64:
</para>
Show replies by date