svn commit: r44300 - head/en_US.ISO8859-1/books/handbook/boot
Dru Lavigne
dru at FreeBSD.org
Thu Mar 20 17:07:36 UTC 2014
Author: dru
Date: Thu Mar 20 17:07:35 2014
New Revision: 44300
URL: http://svnweb.freebsd.org/changeset/doc/44300
Log:
Initial prep work for Booting Process chapter.
Sponsored by: iXsystems
Modified:
head/en_US.ISO8859-1/books/handbook/boot/chapter.xml
Modified: head/en_US.ISO8859-1/books/handbook/boot/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Thu Mar 20 15:55:58 2014 (r44299)
+++ head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Thu Mar 20 17:07:35 2014 (r44300)
@@ -153,14 +153,11 @@
have been configured to run on a &os; system at startup.</para>
</sect1>
- <sect1 xml:id="boot-blocks">
+ <sect1 xml:id="boot-boot0">
<title>The Boot Manager and Boot Stages</title>
<indexterm><primary>Boot Manager</primary></indexterm>
- <sect2 xml:id="boot-boot0">
- <title>The Boot Manager</title>
-
<indexterm><primary>Master Boot Record
(<acronym>MBR</acronym>)</primary></indexterm>
@@ -236,11 +233,10 @@ label=FreeBSD</programlisting>
run <command>/sbin/lilo -v</command> to commit the new
changes. Verify these are correct by checking the screen
messages.</para>
- </sect2>
<sect2 xml:id="boot-boot1">
- <title>Stage One, <filename>/boot/boot1</filename>, and Stage
- Two, <filename>/boot/boot2</filename></title>
+ <title>Stage One and Stage
+ Two</title>
<para>Conceptually, the first and second stages are part of the
same program, on the same area of the disk. Because of space
@@ -305,7 +301,7 @@ boot:</screen>
</sect2>
<sect2 xml:id="boot-loader">
- <title>Stage Three, <filename>/boot/loader</filename></title>
+ <title>Stage Three</title>
<indexterm><primary>boot-loader</primary></indexterm>
@@ -318,9 +314,6 @@ boot:</screen>
more powerful interpreter which has a more complex command
set.</para>
- <sect3 xml:id="boot-loader-flow">
- <title>Loader Program Flow</title>
-
<para>During initialization, the loader will probe for a
console and for disks, and figure out which disk it is
booting from. It will set variables accordingly, and an
@@ -345,7 +338,6 @@ boot:</screen>
prompt which understands the command set, where the user may
adjust variables, unload all modules, load modules, and then
finally boot or reboot.</para>
- </sect3>
<sect3 xml:id="boot-loader-commands">
<title>Loader Built-In Commands</title>
@@ -545,10 +537,88 @@ boot:</screen>
</listitem>
</itemizedlist>
</sect3>
+ </sect2>
+
+ <sect2 xml:id="boot-kernel">
+ <title>Kernel Interaction During Boot</title>
+
+ <indexterm>
+ <primary>kernel</primary>
+ <secondary>boot interaction</secondary>
+ </indexterm>
+
+ <para>Once the kernel is loaded by either the default loader
+ or by boot2,
+ which bypasses the loader, it
+ examines any boot flags and adjusts its behavior as
+ necessary.</para>
+
+ <indexterm>
+ <primary>kernel</primary>
+ <secondary>bootflags</secondary>
+ </indexterm>
+
+ <para>Here are the more common boot flags:</para>
+
+ <variablelist xml:id="boot-kernel-bootflags-list">
+ <varlistentry>
+ <term><option>-a</option></term>
+
+ <listitem>
+ <para>During kernel initialization, ask for the device
+ to mount as the root file system.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-C</option></term>
+
+ <listitem>
+ <para>Boot from CDROM.</para>
+ </listitem>
+ </varlistentry>
- <sect3 xml:id="boot-splash">
+ <varlistentry>
+ <term><option>-c</option></term>
+
+ <listitem>
+ <para>Run UserConfig, the boot-time kernel
+ configurator.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-s</option></term>
+
+ <listitem>
+ <para>Boot into single-user mode.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-v</option></term>
+
+ <listitem>
+ <para>Be more verbose during kernel startup.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <note>
+ <para>Refer to &man.boot.8; for more information on the other
+ boot flags.</para>
+ </note>
+ </sect2>
+
+<!-- <sect2 id="boot-kernel-userconfig">
+ <title>UserConfig: the Boot-time Kernel Configurator</title>
+
+ <para> </para>
+ </sect2> -->
+
+ <sect2 xml:id="boot-splash">
<info>
- <title>Boot Time Splash Screens</title>
+ <title>Configuring Boot Time Splash Screens</title>
<authorgroup>
<author>
@@ -575,9 +645,6 @@ boot:</screen>
and configure a graphical display manager and a graphical
login manager.</para>
- <sect4 xml:id="boot-splash-function">
- <title>Splash Screen Function</title>
-
<para>The splash screen function supports 256-colors in the
bitmap (<filename>.bmp</filename>), ZSoft
<acronym>PCX</acronym> (<filename>.pcx</filename>), or
@@ -622,10 +689,6 @@ boot:</screen>
<package>sysutils/bsd-splash-changer</package> port,
splash images can be chosen from a collection randomly at
each boot.</para>
- </sect4>
-
- <sect4 xml:id="boot-splash-enable">
- <title>Enabling the Splash Screen Function</title>
<para>The splash screen <filename>.bmp</filename>,
<filename>.pcx</filename>, or <filename>.bin</filename>
@@ -710,92 +773,9 @@ bitmap_name="<replaceable>/boot/splash.b
<para>For more information, refer to &man.splash.4;,
&man.loader.conf.5;, and &man.vga.4;.</para>
- </sect4>
- </sect3>
</sect2>
</sect1>
- <sect1 xml:id="boot-kernel">
- <title>Kernel Interaction During Boot</title>
-
- <indexterm>
- <primary>kernel</primary>
- <secondary>boot interaction</secondary>
- </indexterm>
-
- <para>Once the kernel is loaded by either the default loader
- (<xref linkend="boot-loader"/>) or by boot2
- (<xref linkend="boot-boot1"/>), which bypasses the loader, it
- examines any boot flags and adjusts its behavior as
- necessary.</para>
-
- <sect2 xml:id="boot-kernel-bootflags">
- <title>Kernel Boot Flags</title>
-
- <indexterm>
- <primary>kernel</primary>
- <secondary>bootflags</secondary>
- </indexterm>
-
- <para>Here are the more common boot flags:</para>
-
- <variablelist xml:id="boot-kernel-bootflags-list">
- <varlistentry>
- <term><option>-a</option></term>
-
- <listitem>
- <para>During kernel initialization, ask for the device
- to mount as the root file system.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>-C</option></term>
-
- <listitem>
- <para>Boot from CDROM.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>-c</option></term>
-
- <listitem>
- <para>Run UserConfig, the boot-time kernel
- configurator.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>-s</option></term>
-
- <listitem>
- <para>Boot into single-user mode.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>-v</option></term>
-
- <listitem>
- <para>Be more verbose during kernel startup.</para>
- </listitem>
- </varlistentry>
- </variablelist>
-
- <note>
- <para>Refer to &man.boot.8; for more information on the other
- boot flags.</para>
- </note>
- </sect2>
-
-<!-- <sect2 id="boot-kernel-userconfig">
- <title>UserConfig: the Boot-time Kernel Configurator</title>
-
- <para> </para>
- </sect2> -->
- </sect1>
-
<sect1 xml:id="device-hints">
<info>
<title>Device Hints</title>
@@ -905,16 +885,12 @@ bitmap_name="<replaceable>/boot/splash.b
in the <envar>init_path</envar> variable in
<command>loader</command>.</para>
- <sect2 xml:id="boot-autoreboot">
- <title>Automatic Reboot Sequence</title>
-
- <para>The automatic reboot sequence makes sure that the file
+ <para>The boot sequence makes sure that the file
systems available on the system are consistent. If they are
not, and &man.fsck.8; cannot fix the inconsistencies of a UFS
file system, &man.init.8; drops the system into single-user
- mode (<xref linkend="boot-singleuser"/>) so that the system
+ mode so that the system
administrator can resolve the problem directly.</para>
- </sect2>
<sect2 xml:id="boot-singleuser">
<title>Single-User Mode</title>
@@ -923,7 +899,7 @@ bitmap_name="<replaceable>/boot/splash.b
<indexterm><primary>console</primary></indexterm>
<para>This mode can be reached through the automatic reboot
- sequence (<xref linkend="boot-autoreboot"/>), the user booting
+ sequence, the user booting
with <option>-s</option>, or by setting the <envar>boot_
single</envar> variable in &man.loader.8;.</para>
@@ -970,9 +946,6 @@ console none
multi-user mode, in which it starts the resource configuration
of the system.</para>
- <sect3 xml:id="boot-rc">
- <title>Resource Configuration</title>
-
<indexterm><primary>rc files</primary></indexterm>
<para>The resource configuration system reads in
@@ -988,7 +961,6 @@ console none
<para>To learn more about the resource configuration system,
refer to &man.rc.8; and examine the scripts
themselves.</para>
- </sect3>
</sect2>
</sect1>
More information about the svn-doc-all
mailing list