commit 196eae072a477e7492e46a62a3fbe5d689fcabb4 Author: Stephen Wadeley swadeley@redhat.com Date: Fri Aug 14 14:22:34 2015 +0200
Customizing the GRUB 2 Configuration File
Renamed the section and removed temporary change info as that is now in the new section about temporary changes.
en-US/Working_with_the_GRUB_2_Boot_Loader.xml | 25 ++++++++++--------------- 1 files changed, 10 insertions(+), 15 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 f7ca789..81f951b 100644 --- a/en-US/Working_with_the_GRUB_2_Boot_Loader.xml +++ b/en-US/Working_with_the_GRUB_2_Boot_Loader.xml @@ -231,8 +231,8 @@ title=Red Hat Enterprise Linux Server (3.10.0-229.4.2.el7.x86_64) 7.0 (Maipo)</s </para> </section>
-<section id="sec-Customizing_the_GRUB_2_Menu"> -<title>Customizing the GRUB 2 Menu</title> +<section id="sec-Customizing_the_GRUB_2_Configuration_File"> +<title>Customizing the GRUB 2 Configuration File</title> <para> GRUB 2 scripts search the user's computer and build a boot menu based on what operating systems the scripts find. To reflect the latest system boot options, the boot menu is rebuilt automatically when the kernel is updated or a new kernel is added. </para> @@ -303,6 +303,9 @@ The <literal>DEFAULTKERNEL</literal> directive specifies what package type will <para> To force a system to always use a particular menu entry, use the menu entry name as the key to the <literal>GRUB_DEFAULT</literal> directive in the <filename>/etc/default/grub</filename> file. To list the available menu entries, run the following command as <systemitem class="username">root</systemitem>: <screen>~]# <command>awk -F' '$1=="menuentry " {print $2}' /etc/grub2.cfg</command></screen> + The file name <filename>/etc/grub2.cfg</filename> is a symlink to the <filename>grub.cfg</filename> file, whose location is architecture dependent. For reliability reasons, the symlink is not used in other examples in this chapter. It is better to use absolute paths when writing to a file, especially when repairing a system. + </para> + <para> Changes to <filename>/etc/default/grub</filename> require rebuilding the <filename>grub.cfg</filename> file as follows:</para> <itemizedlist> <listitem> @@ -319,19 +322,11 @@ The <literal>DEFAULTKERNEL</literal> directive specifies what package type will </listitem> </itemizedlist> </section> - <section id="sec-Editing_an_Entry"> - <title>Editing an Entry</title> - <bridgehead>Kernel Parameters</bridgehead> - <para> - To use a kernel parameter only during a single boot process, when the GRUB 2 boot menu appears, move the cursor to the kernel you want to start, and press the <keycap>e</keycap> key to edit the kernel parameters. For example, to run the system in emergency mode, add the <emphasis>emergency</emphasis> parameter at the end of the <literal>linux16</literal> line: - </para> -<screen>linux16 /vmlinuz-3.17.4-301.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 emergency</screen> - <para> - These settings are not persistent and apply only for a single boot. To make the settings persistent, edit values of the <systemitem>GRUB_CMDLINE_LINUX</systemitem> key in the <filename>/etc/default/grub</filename> file. For example, if you want to enable emergency mode for each boot, use: - </para> -<screen>GRUB_CMDLINE_LINUX="emergency"</screen> - <para> - Note that you can specify multiple parameters for the <systemitem>GRUB_CMDLINE_LINUX</systemitem> key, similarly to adding the parameters in the GRUB 2 boot menu. For example: + + <section id="sec-Editing_a_Menu_Entry"> + <title>Editing a Menu Entry</title> + <para> + If required to prepare a new GRUB 2 file with different parameters, edit the values of the <systemitem>GRUB_CMDLINE_LINUX</systemitem> key in the <filename>/etc/default/grub</filename> file. Note that you can specify multiple parameters for the <systemitem>GRUB_CMDLINE_LINUX</systemitem> key. For example: <synopsis>GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,9600n8"</synopsis> Where <option>console=tty0</option> is the first virtual terminal and <option>console=ttyS0</option> is the serial terminal to be used. </para>
docs-commits@lists.fedoraproject.org