diff options
Diffstat (limited to 'en_US.ISO8859-1/books/handbook/boot/chapter.xml')
-rw-r--r-- | en_US.ISO8859-1/books/handbook/boot/chapter.xml | 152 |
1 files changed, 69 insertions, 83 deletions
diff --git a/en_US.ISO8859-1/books/handbook/boot/chapter.xml b/en_US.ISO8859-1/books/handbook/boot/chapter.xml index 1af00bc7cc..5dd39b3640 100644 --- a/en_US.ISO8859-1/books/handbook/boot/chapter.xml +++ b/en_US.ISO8859-1/books/handbook/boot/chapter.xml @@ -4,11 +4,10 @@ $FreeBSD$ --> - -<chapter id="boot"> +<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="boot"> <title>The &os; Booting Process</title> - <sect1 id="boot-synopsis"> + <sect1 xml:id="boot-synopsis"> <title>Synopsis</title> <indexterm><primary>booting</primary></indexterm> @@ -54,7 +53,7 @@ </note> </sect1> - <sect1 id="boot-introduction"> + <sect1 xml:id="boot-introduction"> <title>The Booting Problem</title> <para>Turning on a computer and starting the operating system @@ -150,12 +149,12 @@ have been configured to run on a &os; system at startup.</para> </sect1> - <sect1 id="boot-blocks"> + <sect1 xml:id="boot-blocks"> <title>The Boot Manager and Boot Stages</title> <indexterm><primary>Boot Manager</primary></indexterm> - <sect2 id="boot-boot0"> + <sect2 xml:id="boot-boot0"> <title>The Boot Manager</title> <indexterm><primary>Master Boot Record @@ -182,7 +181,7 @@ will be displayed at boot time:</para> </formalpara> - <example id="boot-boot0-example"> + <example xml:id="boot-boot0-example"> <title><filename>boot0</filename> Screenshot</title> <screen>F1 Win @@ -197,14 +196,14 @@ Default: F2</screen> existing <acronym>MBR</acronym> with the &os; <acronym>MBR</acronym>, use the following command:</para> - <screen>&prompt.root; <userinput>fdisk -B -b /boot/boot0 <replaceable>device</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>fdisk -B -b /boot/boot0 device</userinput></screen> <para>where <replaceable>device</replaceable> is the boot disk, - such as <devicename>ad0</devicename> for the first - <acronym>IDE</acronym> disk, <devicename>ad2</devicename> + such as <filename>ad0</filename> for the first + <acronym>IDE</acronym> disk, <filename>ad2</filename> for the first <acronym>IDE</acronym> disk on a second <acronym>IDE</acronym> controller, or - <devicename>da0</devicename> + <filename>da0</filename> for the first <acronym>SCSI</acronym> disk. To create a custom configuration of the <acronym>MBR</acronym>, refer to &man.boot0cfg.8;.</para> @@ -235,7 +234,7 @@ label=FreeBSD</programlisting> messages.</para> </sect2> - <sect2 id="boot-boot1"> + <sect2 xml:id="boot-boot1"> <title>Stage One, <filename>/boot/boot1</filename>, and Stage Two, <filename>/boot/boot2</filename></title> @@ -269,7 +268,7 @@ label=FreeBSD</programlisting> provides a boot configuration which is run by <filename>boot2</filename>.</para> - <example id="boot-boot2-example"> + <example xml:id="boot-boot2-example"> <title><filename>boot2</filename> Screenshot</title> <screen>>> FreeBSD/i386 BOOT @@ -281,10 +280,10 @@ boot:</screen> <filename>boot1</filename> and <filename>boot2</filename>:</para> - <screen>&prompt.root; <userinput>bsdlabel -B <replaceable>diskslice</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>bsdlabel -B diskslice</userinput></screen> <para>where <replaceable>diskslice</replaceable> is the disk and - slice to boot from, such as <devicename>ad0s1</devicename> + slice to boot from, such as <filename>ad0s1</filename> for the first slice on the first <acronym>IDE</acronym> disk.</para> @@ -292,7 +291,7 @@ boot:</screen> <title>Dangerously Dedicated Mode</title> <para>If just the disk name is used, such as - <devicename>ad0</devicename>, &man.bsdlabel.8; will create a + <filename>ad0</filename>, &man.bsdlabel.8; will create a <quote>dangerously dedicated</quote> disk, without slices. This is probably not the desired action, so double check the <replaceable>diskslice</replaceable> passed to @@ -301,7 +300,7 @@ boot:</screen> </warning> </sect2> - <sect2 id="boot-loader"> + <sect2 xml:id="boot-loader"> <title>Stage Three, <filename>/boot/loader</filename></title> <indexterm><primary>boot-loader</primary></indexterm> @@ -315,7 +314,7 @@ boot:</screen> more powerful interpreter which has a more complex command set.</para> - <sect3 id="boot-loader-flow"> + <sect3 xml:id="boot-loader-flow"> <title>Loader Program Flow</title> <para>During initialization, the loader will probe for a @@ -344,7 +343,7 @@ boot:</screen> finally boot or reboot.</para> </sect3> - <sect3 id="boot-loader-commands"> + <sect3 xml:id="boot-loader-commands"> <title>Loader Built-In Commands</title> <para>These are the most commonly used loader commands. For a @@ -365,8 +364,8 @@ boot:</screen> <varlistentry> <term>boot - <optional><replaceable>-options</replaceable></optional> - <optional><replaceable>kernelname</replaceable></optional></term> + <optional>-options</optional> + <optional>kernelname</optional></term> <listitem> <para>Immediately proceeds to boot the kernel, with any @@ -392,7 +391,7 @@ boot:</screen> <varlistentry> <term>help - <optional><replaceable>topic</replaceable></optional></term> + <optional>topic</optional></term> <listitem> <para>Shows help messages read from @@ -414,8 +413,8 @@ boot:</screen> </varlistentry> <varlistentry> - <term>load <optional><option>-t</option> - <replaceable>type</replaceable></optional> + <term>load <optional>-t + type</optional> <replaceable>filename</replaceable></term> <listitem> @@ -427,8 +426,8 @@ boot:</screen> </varlistentry> <varlistentry> - <term>ls <optional><option>-l</option></optional> - <optional><replaceable>path</replaceable></optional></term> + <term>ls <optional>-l</optional> + <optional>path</optional></term> <listitem> <para>Displays a listing of files in the given path, or @@ -440,7 +439,7 @@ boot:</screen> <varlistentry> <term>lsdev - <optional><option>-v</option></optional></term> + <optional>-v</optional></term> <listitem> <para>Lists all of the devices from which it may be @@ -451,7 +450,7 @@ boot:</screen> <varlistentry> <term>lsmod - <optional><option>-v</option></optional></term> + <optional>-v</optional></term> <listitem> <para>Displays loaded modules. If <option>-v</option> @@ -496,7 +495,7 @@ boot:</screen> </variablelist> </sect3> - <sect3 id="boot-loader-examples"> + <sect3 xml:id="boot-loader-examples"> <title>Loader Examples</title> <para>Here are some practical examples of loader usage:</para> @@ -515,7 +514,7 @@ boot:</screen> load the previous or another kernel:</para> <screen><userinput>unload</userinput> -<userinput>load <replaceable>kernel.old</replaceable></userinput></screen> +<userinput>load kernel.old</userinput></screen> <para>Use <filename>kernel.GENERIC</filename> to refer to the default kernel that comes with an installation, or @@ -530,7 +529,7 @@ boot:</screen> another kernel:</para> <screen><userinput>unload</userinput> -<userinput>set kernel="<replaceable>kernel.old</replaceable>"</userinput> +<userinput>set kernel="kernel.old"</userinput> <userinput>boot-conf</userinput></screen></note> </listitem> @@ -538,23 +537,19 @@ boot:</screen> <para>To load an automated kernel configuration script:</para> - <screen><userinput>load -t userconfig_script <replaceable>/boot/kernel.conf</replaceable></userinput></screen> + <screen><userinput>load -t userconfig_script /boot/kernel.conf</userinput></screen> </listitem> </itemizedlist> </sect3> - <sect3 id="boot-splash"> - <sect3info> + <sect3 xml:id="boot-splash"> + <info><title>Boot Time Splash Screens</title> <authorgroup> - <author> - <firstname>Joseph J.</firstname> - <surname>Barbish</surname> - <contrib>Contributed by </contrib> - </author> + <author><personname><firstname>Joseph J.</firstname><surname>Barbish</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> - </sect3info> + </info> - <title>Boot Time Splash Screens</title> + <para>The splash screen creates an alternate boot screen. The splash screen hides all the boot probe messages and service @@ -570,7 +565,7 @@ boot:</screen> and configure a graphical display manager and a graphical login manager.</para> - <sect4 id="boot-splash-function"> + <sect4 xml:id="boot-splash-function"> <title>Splash Screen Function</title> <para>The splash screen function supports 256-colors in the @@ -611,21 +606,19 @@ boot:</screen> boot time, even when the splash screen is enabled.</para> <para>Sample splash screen files can be downloaded from the - gallery at <ulink - url="http://artwork.freebsdgr.org/node/3/">http://artwork.freebsdgr.org</ulink>. - By installing the <filename - role="package">sysutils/bsd-splash-changer</filename> + gallery at <link xlink:href="http://artwork.freebsdgr.org/node/3/">http://artwork.freebsdgr.org</link>. + By installing the <package>sysutils/bsd-splash-changer</package> port, splash images can be chosen from a collection randomly at each boot.</para> </sect4> - <sect4 id="boot-splash-enable"> + <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> image has to be placed on the root partition, for example - in <filename class="directory">/boot</filename>.</para> + in <filename>/boot</filename>.</para> <para>For the default boot display resolution of 256-colors and 320 by 200 pixels or less, edit @@ -647,7 +640,7 @@ bitmap_load="YES" bitmap_name="<replaceable>/boot/splash.bmp</replaceable>"</programlisting> <para>This example assumes that - <filename><replaceable>/boot/splash.bmp</replaceable></filename> + <filename>/boot/splash.bmp</filename> is used for the splash screen. To use a <acronym>PCX</acronym> file, use the following statements, plus the <literal>vesa_load="YES"</literal> line, @@ -658,8 +651,7 @@ bitmap_load="YES" bitmap_name="<replaceable>/boot/splash.pcx</replaceable>"</programlisting> <para>Beginning with &os; 8.3, another option is to use - ASCII art in <ulink - url="https://en.wikipedia.org/wiki/TheDraw">TheDraw</ulink> + ASCII art in <link xlink:href="https://en.wikipedia.org/wiki/TheDraw">TheDraw</link> format.</para> <programlisting>splash_txt="YES" @@ -670,9 +662,9 @@ bitmap_name="<replaceable>/boot/splash.bin</replaceable>"</programlisting> <quote>splash</quote> as shown in the above example. It can be anything as long as it is one of the supported types such as, - <filename><replaceable>splash_640x400</replaceable>.bmp</filename> + <filename>splash_640x400.bmp</filename> or - <filename><replaceable>bluewave</replaceable>.pcx</filename>.</para> + <filename>bluewave.pcx</filename>.</para> <para>Other interesting <filename>loader.conf</filename> options include:</para> @@ -710,7 +702,7 @@ bitmap_name="<replaceable>/boot/splash.bin</replaceable>"</programlisting> </sect2> </sect1> - <sect1 id="boot-kernel"> + <sect1 xml:id="boot-kernel"> <title>Kernel Interaction During Boot</title> <indexterm> @@ -719,12 +711,11 @@ bitmap_name="<replaceable>/boot/splash.bin</replaceable>"</programlisting> </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 + (<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 id="boot-kernel-bootflags"> + <sect2 xml:id="boot-kernel-bootflags"> <title>Kernel Boot Flags</title> <indexterm> @@ -734,7 +725,7 @@ bitmap_name="<replaceable>/boot/splash.bin</replaceable>"</programlisting> <para>Here are the more common boot flags:</para> - <variablelist id="boot-kernel-bootflags-list"> + <variablelist xml:id="boot-kernel-bootflags-list"> <varlistentry> <term><option>-a</option></term> @@ -792,19 +783,15 @@ bitmap_name="<replaceable>/boot/splash.bin</replaceable>"</programlisting> </sect1> - <sect1 id="device-hints"> - <sect1info> + <sect1 xml:id="device-hints"> + <info><title>Device Hints</title> <authorgroup> - <author> - <firstname>Tom</firstname> - <surname>Rhodes</surname> - <contrib>Contributed by </contrib> - </author> + <author><personname><firstname>Tom</firstname><surname>Rhodes</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> - <!-- 18 OCT 2002 --> - </sect1info> + + </info> - <title>Device Hints</title> + <indexterm> <primary>device.hints</primary> @@ -817,8 +804,7 @@ bitmap_name="<replaceable>/boot/splash.bin</replaceable>"</programlisting> are used by device drivers for device configuration.</para> <para>Device hints may also be specified at the Stage 3 boot - loader prompt, as demonstrated in <xref - linkend="boot-loader"/>. + loader prompt, as demonstrated in <xref linkend="boot-loader"/>. Variables can be added using <command>set</command>, removed with <command>unset</command>, and viewed <command>show</command>. Variables set in @@ -834,11 +820,11 @@ bitmap_name="<replaceable>/boot/splash.bin</replaceable>"</programlisting> <quote>#</quote> as comment markers. Lines are constructed as follows:</para> - <screen><userinput>hint.driver.unit.keyword="<replaceable>value</replaceable>"</userinput></screen> + <screen><userinput>hint.driver.unit.keyword="value"</userinput></screen> <para>The syntax for the Stage 3 boot loader is:</para> - <screen><userinput>set hint.driver.unit.keyword=<replaceable>value</replaceable></userinput></screen> + <screen><userinput>set hint.driver.unit.keyword=value</userinput></screen> <para>where <literal>driver</literal> is the device driver name, <literal>unit</literal> is the device driver unit number, and @@ -888,7 +874,7 @@ bitmap_name="<replaceable>/boot/splash.bin</replaceable>"</programlisting> &man.kenv.1;, &man.loader.conf.5;, and &man.loader.8;.</para> </sect1> - <sect1 id="boot-init"> + <sect1 xml:id="boot-init"> <title>Init: Process Control Initialization</title> <indexterm> @@ -901,7 +887,7 @@ bitmap_name="<replaceable>/boot/splash.bin</replaceable>"</programlisting> in the <envar>init_path</envar> variable in <command>loader</command>.</para> - <sect2 id="boot-autoreboot"> + <sect2 xml:id="boot-autoreboot"> <title>Automatic Reboot Sequence</title> <para>The automatic reboot sequence makes sure that the file @@ -912,7 +898,7 @@ bitmap_name="<replaceable>/boot/splash.bin</replaceable>"</programlisting> administrator can resolve the problem directly.</para> </sect2> - <sect2 id="boot-singleuser"> + <sect2 xml:id="boot-singleuser"> <title>Single-User Mode</title> <indexterm><primary>single-user mode</primary></indexterm> @@ -929,10 +915,10 @@ bitmap_name="<replaceable>/boot/splash.bin</replaceable>"</programlisting> <para>If the system <literal>console</literal> is set to <literal>insecure</literal> in <filename>/etc/ttys</filename>, - the system will prompt for the <username>root</username> + the system will prompt for the <systemitem class="username">root</systemitem> password before initiating single-user mode.</para> - <example id="boot-insecure-console"> + <example xml:id="boot-insecure-console"> <title>An Insecure Console in <filename>/etc/ttys</filename></title> @@ -947,14 +933,14 @@ console none unknown off insecure</programlisting> <para>An <literal>insecure</literal> console means that physical security to the console is considered to be insecure, so only someone who knows the - <username>root</username> password may use single-user mode. + <systemitem class="username">root</systemitem> password may use single-user mode. Thus, to add this measure of security, choose <literal>insecure</literal>, instead of the default of <literal>secure</literal>.</para> </note> </sect2> - <sect2 id="boot-multiuser"> + <sect2 xml:id="boot-multiuser"> <title>Multi-User Mode</title> <indexterm><primary>multi-user mode</primary></indexterm> @@ -965,7 +951,7 @@ console none unknown off insecure</programlisting> multi-user mode, in which it starts the resource configuration of the system.</para> - <sect3 id="boot-rc"> + <sect3 xml:id="boot-rc"> <title>Resource Configuration</title> <indexterm><primary>rc files</primary></indexterm> @@ -987,7 +973,7 @@ console none unknown off insecure</programlisting> </sect2> </sect1> - <sect1 id="boot-shutdown"> + <sect1 xml:id="boot-shutdown"> <title>Shutdown Sequence</title> <indexterm> @@ -1005,8 +991,8 @@ console none unknown off insecure</programlisting> that support power management, use <command>shutdown -p now</command> to turn the power off immediately. To reboot a &os; system, use <command>shutdown -r now</command>. One must - be <username>root</username> or a member of - <groupname>operator</groupname> in order to run + be <systemitem class="username">root</systemitem> or a member of + <systemitem class="groupname">operator</systemitem> in order to run &man.shutdown.8;. One can also use &man.halt.8; and &man.reboot.8;. Refer to their manual pages and to &man.shutdown.8; for more information.</para> |