commit cca59f692f1803043a0c76bd185c5c846fac61f6
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Mon Jun 17 22:54:31 2013 -0600
updating references to GRUB target selection section
en-US/Boot_Init_Shutdown.xml | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/en-US/Boot_Init_Shutdown.xml b/en-US/Boot_Init_Shutdown.xml
index 73b5cfc..375dc32 100644
--- a/en-US/Boot_Init_Shutdown.xml
+++ b/en-US/Boot_Init_Shutdown.xml
@@ -207,7 +207,7 @@
Once the second stage boot loader has determined which kernel to boot, it locates
the corresponding kernel binary in the <filename>/boot/</filename> directory.
The kernel binary is named using the following format —
<filename>/boot/vmlinuz-<replaceable><kernel-version></replaceable></filename>
file (where
<filename><replaceable><kernel-version></replaceable></filename>
corresponds to the kernel version specified in the boot loader's settings).
</para>
<para>
- The bootloader is also used to pass arguments to the kernel it loads. This allows
the system to operate with a specified root filesystem, enable or disable kernel modules
and system features, or configure booting to a specific runlevel. For instructions on
using the boot loader to supply command line arguments to the kernel, refer to <xref
linkend="ch-grub" />. Specific kernel parameters are described in
<filename>/usr/share/doc/kernel-doc-*/Documentation/kernel-parameters.txt</filename>,
which is provided by the <package>kernel-doc</package> package. For
information on changing the runlevel at the boot loader prompt, refer <xref
linkend="s1-grub-runlevels" />.
+ The bootloader is also used to pass arguments to the kernel it loads. This allows
the system to operate with a specified root filesystem, enable or disable kernel modules
and system features, or configure booting to a specific runlevel. For instructions on
using the boot loader to supply command line arguments to the kernel, refer to <xref
linkend="ch-grub" />. Specific kernel parameters are described in
<filename>/usr/share/doc/kernel-doc-*/Documentation/kernel-parameters.txt</filename>,
which is provided by the <package>kernel-doc</package> package. For
information on changing the target at the boot loader prompt, refer <xref
linkend="s1-grub-targets" />.
</para>
<para>
The boot loader then places one or more appropriate
<filename>initramfs</filename> images into memory. The
<filename>initramfs</filename> is used by the kernel to load drivers and
modules necessary to boot the system.
@@ -380,7 +380,7 @@ Let's look at the different types of units:
<application>systemd</application> replaces traditional
<application>SysVinit</application> <function>runlevels</function>
with predefined groups of <function>units</function> called
<function>targets</function>. <function>Targets</function> are
usually defined according to the intended use of the system, and ensure that required
dependencies for that use are met.
</para>
<para>
- The system boots to the target described in
<filename>/lib/systemd/system/default.target</filename>. This file is a
symlink that can be changed when booting to a different target is desired. Appending
<command>systemd.unit=<replaceable>custom</replaceable>.target</command>
to the kernel's boot arguments will override the default target.
+ The system boots to the target described in
<filename>/lib/systemd/system/default.target</filename>. This file is a
symlink that can be changed when booting to a different target is desired. Appending
<command>systemd.unit=<replaceable>custom</replaceable>.target</command>
to the kernel's boot arguments will override the default target. Refer to <xref
linkend="s1-grub-targets" /> for detailed instructions.
</para>
<para>
The following table shows some standard preconfigured targets, the
<application>sysVinit</application> <function>runlevels</function>
they resemble and the use case they address.
Show replies by date