commit 5f0dbe079cc304862368083866dbf0a9f53b6dd7
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Fri Aug 14 14:16:11 2015 +0200
Making Temporary Changes to a GRUB 2 Menu
New section to separate the tasks
en-US/Working_with_the_GRUB_2_Boot_Loader.xml | 38 +++++++++++++++++++++++++
1 files changed, 38 insertions(+), 0 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 c06c73b..9ac2fb2 100644
--- a/en-US/Working_with_the_GRUB_2_Boot_Loader.xml
+++ b/en-US/Working_with_the_GRUB_2_Boot_Loader.xml
@@ -106,6 +106,44 @@ menuentry 'Fedora, with Linux 3.17.4-301.fc21.x86_64' --class
fedora --class gnu
</para>
</section>
+ <section id="sec-Making_Temporary_Changes_to_a_GRUB_2_Menu">
+ <title>Making Temporary Changes to a GRUB 2 Menu</title>
+
+ <procedure
id="proc-Making_Temporary_Changes_to_Kernel_Menu_Entry">
+ <title>Making Temporary Changes to a Kernel Menu Entry</title>
+ <para>
+ To change kernel parameters only during a single boot process, proceed as follows:
+ </para>
+ <step>
+ <para>
+ Start the system and, on the GRUB 2 boot screen, move the cursor to the menu entry
you want to edit, and press the <keycap>e</keycap> key for edit.
+ </para>
+ </step>
+ <step>
+ <para>
+ Move the cursor down to find the kernel command line. The kernel command line
starts with <literal>linux</literal> on 64-Bit IBM Power Series,
<literal>linux16</literal> on x86-64 BIOS-based systems, or
<literal>linuxefi</literal> on UEFI systems.
+ </para>
+ </step>
+ <step>
+ <para>
+ Move the cursor to the end of the line.
+ </para>
+ <para>
+ Press
<keycombo><keycap>Ctrl</keycap><keycap>a</keycap></keycombo>
and
<keycombo><keycap>Ctrl</keycap><keycap>e</keycap></keycombo>
to jump to the start and end of the line, respectively. On some systems,
<keycap>Home</keycap> and <keycap>End</keycap> might also work.
+</para>
+</step>
+<step>
+ <para>
+ Edit the kernel parameters as required. For example, to run the system in
emergency mode, add the <emphasis>emergency</emphasis> parameter at the end of
the <literal>linux16</literal> line:
+<screen>linux16 /vmlinuz-3.10.0-0.rc4.59.el7.x86_64 root=/dev/mapper/rhel-root
ro rd.md=0 rd.dm=0 rd.lvm.lv=rhel/swap crashkernel=auto rd.luks=0 vconsole.keymap=us
rd.lvm.lv=rhel/root rhgb quiet <emphasis
role="bold">emergency</emphasis></screen>
+The <option>rhgb</option> and <option>quiet</option> parameters
can be removed in order to enable system messages.
+ </para>
+ <para>
+ These settings are not persistent and apply only for a single boot. To make
persistent changes to a menu entry on a system, use the
<command>grubby</command> tool. See <xref
linkend="bh-Adding_and_Removing_Arguments_from_a_GRUB_Menu_Entry" /> for more
information on using <command>grubby</command>.
+ </para>
+</step>
+</procedure>
+</section>
<para>
The <command>grubby</command> tool can be used to read information from,
and make persistent changes to, the <filename>grub.cfg</filename> file. It
enables, for example, changing GRUB menu entries to specify what arguments to pass to a
kernel on system start and changing the default kernel.<remark> IS THIS BIT
TRUE?</remark> In Red Hat Enterprise Linux 7,
<command>grubby</command> defaults to working with the GRUB 2 configuration
file, <filename>grub.cfg</filename>.<remark> Do we need to warn users
to use the "--grub2" option in scripts?</remark>
</para>
Show replies by date