Date: Thu, 9 May 2013 16:23:02 +0000 (UTC) From: Dru Lavigne <dru@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41576 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/boot Message-ID: <201305091623.r49GN2pV038934@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: dru Date: Thu May 9 16:23:02 2013 New Revision: 41576 URL: http://svnweb.freebsd.org/changeset/doc/41576 Log: This patch addresses the following: - fix command/app tags which should be entities - fix link tags - add acronym tags A subsequent patch will fix the white space. Approved by: bcr (mentor) Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/boot/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/boot/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/boot/chapter.xml Thu May 9 13:39:38 2013 (r41575) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/boot/chapter.xml Thu May 9 16:23:02 2013 (r41576) @@ -73,47 +73,60 @@ to the mechanism used to load the operating system, which has become shortened to <quote>booting</quote>.</para> - <indexterm><primary>BIOS</primary></indexterm> + <indexterm><primary><acronym>BIOS</acronym></primary></indexterm> <indexterm> <primary>Basic Input/Output System</primary> - <see>BIOS</see> + <see><acronym>BIOS</acronym></see> </indexterm> - <para>On x86 hardware the Basic Input/Output System (BIOS) is + <para>On x86 hardware the Basic Input/Output System + (<acronym>BIOS</acronym>) is responsible for loading the operating system. To do this, the - BIOS looks on the hard disk for the Master Boot Record (MBR), - which must be located on a specific place on the disk. The BIOS - has enough knowledge to load and run the MBR, and assumes that - the MBR can then carry out the rest of the tasks involved in + <acronym>BIOS</acronym> looks on the hard disk for the Master + Boot Record (<acronym>MBR</acronym>), + which must be located on a specific place on the disk. The + <acronym>BIOS</acronym> + has enough knowledge to load and run the <acronym>MBR</acronym>, + and assumes that + the <acronym>MBR</acronym> can then carry out the rest of the + tasks involved in loading the operating system, possibly with the help of the - BIOS.</para> + <acronym>BIOS</acronym>.</para> - <indexterm><primary>Master Boot Record (MBR)</primary></indexterm> + <indexterm><primary>Master Boot Record + <acronym>MBR</acronym>)</primary></indexterm> <indexterm><primary>Boot Manager</primary></indexterm> <indexterm><primary>Boot Loader</primary></indexterm> - <para>The code within the MBR is usually referred to as a + <para>The code within the <acronym>MBR</acronym> is usually + referred to as a <emphasis>boot manager</emphasis>, especially when it interacts - with the user. In this case the boot manager usually has more + with the user. In this case, the boot manager usually has more code in the first <emphasis>track</emphasis> of the disk or - within some OS's file system. (A boot manager is sometimes also + within the file system of some operating systems. A boot + manager is sometimes also called a <emphasis>boot loader</emphasis>, but &os; uses that - term for a later stage of booting.) Popular boot managers - include <application>boot0</application> (aka + term for a later stage of booting. Popular boot managers + include <application>boot0</application>, also called <application>Boot Easy</application>, the standard &os; boot - manager), <application>Grub</application>, + manager, <application>Grub</application>, <application>GAG</application>, and - <application>LILO</application>. (Only - <application>boot0</application> fits within the MBR.)</para> - - <para>If only one operating system is installed, a standard PC MBR - will suffice. This MBR searches for the first bootable (active) + <application>LILO</application>. Only + <application>boot0</application> fits within the + <acronym>MBR</acronym>.</para> + + <para>If only one operating system is installed, a standard PC + <acronym>MBR</acronym> + will suffice. This <acronym>MBR</acronym> searches for the + first bootable (active) slice on the disk, and then runs the code on that slice to load - the remainder of the operating system. By default, the MBR - installed by &man.fdisk.8; is such an MBR and is based on + the remainder of the operating system. By default, the + <acronym>MBR</acronym> + installed by &man.fdisk.8; is such an <acronym>MBR</acronym> and + is based on <filename>/boot/mbr</filename>.</para> <para>If multiple operating systems are present, a different boot @@ -122,7 +135,8 @@ boot managers are discussed in the next subsection.</para> <para>The remainder of the &os; bootstrap system is divided - into three stages. The first stage is run by the MBR, which + into three stages. The first stage is run by the + <acronym>MBR</acronym>, which knows just enough to get the computer into a specific state and run the second stage. The second stage can do a little bit more, before running the third stage. The third stage finishes @@ -133,7 +147,7 @@ loader.</para> <indexterm><primary>kernel</primary></indexterm> - <indexterm><primary><command>init</command></primary></indexterm> + <indexterm><primary>&man.init.8;</primary></indexterm> <para>The kernel is then started and it begins to probe for devices and initialize them for use. Once the kernel boot @@ -154,9 +168,10 @@ <title>The Boot Manager</title> <indexterm><primary>Master Boot Record - (MBR)</primary></indexterm> + (<acronym>MBR</acronym>)</primary></indexterm> - <para>The code in the MBR or boot manager is sometimes referred + <para>The code in the <acronym>MBR</acronym> or boot manager is + sometimes referred to as <emphasis>stage zero</emphasis> of the boot process. This section discusses two boot managers: <application>boot0</application> and @@ -166,12 +181,13 @@ <title>The <application>boot0</application> Boot Manager:</title> - <para>The MBR installed by &os;'s installer or + <para>The <acronym>MBR</acronym> installed by &os;'s installer + or &man.boot0cfg.8; is based on <filename>/boot/boot0</filename>. The size and capability of <application>boot0</application> is restricted to 446 bytes due to the slice table and <literal>0x55AA</literal> - identifier at the end of the MBR. If + identifier at the end of the <acronym>MBR</acronym>. If <application>boot0</application> and multiple operating systems are installed, a message similar to this example will be displayed at boot time:</para> @@ -187,18 +203,25 @@ Default: F2</screen> </example> <para>Other operating systems, in particular &windows;, will - overwrite an existing MBR if they are installed after &os;. - If this happens, or you want to replace the existing MBR - with the &os; MBR, use the following command:</para> + overwrite an existing <acronym>MBR</acronym> if they are + installed after &os;. + If this happens, or to replace the 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> <para>where <replaceable>device</replaceable> is the boot disk, - such as <devicename>ad0</devicename> for the first IDE disk, - <devicename>ad2</devicename> for the first IDE disk on a - second IDE controller, or <devicename>da0</devicename> - for the first SCSI disk. To create a custom configuration of - the MBR, refer to &man.boot0cfg.8;.</para> + such as <devicename>ad0</devicename> for the first + <acronym>IDE</acronym> disk, + <devicename>ad2</devicename> for the first + <acronym>IDE</acronym> disk on a + second <acronym>IDE</acronym> controller, or + <devicename>da0</devicename> + for the first <acronym>SCSI</acronym> disk. To create a + custom configuration of + the <acronym>MBR</acronym>, refer to &man.boot0cfg.8;.</para> <formalpara> <title>The LILO Boot Manager:</title> @@ -235,11 +258,11 @@ label=FreeBSD</programlisting> constraints, they have been split into two, but are always installed together. They are copied from the combined <filename>/boot/boot</filename> by the installer or - <application>bsdlabel</application>.</para> + &man.bsdlabel.8;.</para> <para>They are located outside file systems, in the first track of the boot slice, starting with the first sector. This is - where <link linkend="boot-boot0">boot0</link>, or any other + where boot0 (<xref linkend="boot-boot0"/>), or any other boot manager, expects to find a program to run which will continue the boot process. The number of sectors used is easily determined from the size of @@ -256,7 +279,7 @@ label=FreeBSD</programlisting> can provide a simple interface to choose the kernel or loader to run.</para> - <para><link linkend="boot-loader">loader</link> is much more + <para>However, &man.loader.8; is much more sophisticated and provides a boot configuration which is run by <filename>boot2</filename>.</para> @@ -276,7 +299,8 @@ boot:</screen> <para>where <replaceable>diskslice</replaceable> is the disk and slice to boot from, such as <devicename>ad0s1</devicename> - for the first slice on the first IDE disk.</para> + for the first slice on the first <acronym>IDE</acronym> + disk.</para> <warning> <title>Dangerously Dedicated Mode</title> @@ -557,8 +581,8 @@ boot:</screen> first is the default legacy virtual console command line environment. After the system finishes booting, a console login prompt is presented. The second environment is the - graphical environment provided by - <link linkend="x11">Xorg</link>. Refer to that chapter for + graphical environment as described in + <xref linkend="x11"/>. Refer to that chapter for more information on how to install and configure a graphical display manager and a graphical login manager.</para> @@ -574,8 +598,8 @@ boot:</screen> <para>To use larger images, up to the maximum resolution of 1024 by 768 pixels, load the <acronym>VESA</acronym> - module during system boot. For a <ulink - url="kernelconfig">custom kernel</ulink>, include the + module during system boot. For a custom kernel, as + described in <xref linkend="kernelconfig"/>, include the <literal>VESA</literal> kernel configuration option. Loading <acronym>VESA</acronym> support provides the ability to display a splash screen image that fills the @@ -710,10 +734,10 @@ bitmap_name="<replaceable>/boot/splash.b <secondary>boot interaction</secondary> </indexterm> - <para>Once the kernel is loaded by either the default <link - linkend="boot-loader">loader</link> or by <link - linkend="boot-boot1">boot2</link> which bypasses the loader, - it examines its boot flags, if any, and adjusts its behavior as + <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 id="boot-kernel-bootflags"> @@ -807,8 +831,9 @@ bitmap_name="<replaceable>/boot/splash.b <quote>device hints</quote>. These <quote>device hints</quote> are used by device drivers for device configuration.</para> - <para>Device hints may also be specified at the <link - linkend="boot-loader"> Stage 3 boot loader</link> prompt. + <para>Device hints may also be specified at the Stage 3 boot + 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 @@ -882,7 +907,7 @@ bitmap_name="<replaceable>/boot/splash.b <title>Init: Process Control Initialization</title> <indexterm> - <primary><command>init</command></primary> + <primary>&man.init.8;</primary> </indexterm> <para>Once the kernel has finished booting, it passes control to @@ -897,8 +922,8 @@ bitmap_name="<replaceable>/boot/splash.b <para>The automatic reboot 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 - <link linkend="boot-singleuser">single-user mode</link> so + file system, &man.init.8; drops the system into single-user + mode (<xref linkend="boot-singleuser"/>) so that the system administrator can resolve the problem directly.</para> </sect2> @@ -909,14 +934,14 @@ bitmap_name="<replaceable>/boot/splash.b <indexterm><primary>single-user mode</primary></indexterm> <indexterm><primary>console</primary></indexterm> - <para>This mode can be reached through the <link - linkend="boot-autoreboot">automatic reboot sequence</link>, + <para>This mode can be reached through the automatic reboot + sequence (<xref linkend="boot-autoreboot"/>), the user booting with <option>-s</option>, or by setting the <envar>boot_single</envar> variable in - <command>loader</command>.</para> + &man.loader.8;.</para> <para>It can also be reached by calling &man.shutdown.8; from - <link linkend="boot-multiuser">multi-user mode</link> without + multi-user mode (<xref linkend="boot-multiuser"/>) without including <option>-r</option> or <option>-h</option>.</para> <para>If the system <literal>console</literal> is set to @@ -952,8 +977,8 @@ console none <indexterm><primary>multi-user mode</primary></indexterm> <para>If &man.init.8; finds the file systems to be in order, or - once the user has finished their commands in <link - linkend="boot-singleuser">single-user mode</link>, the + once the user has finished their commands in single-user + mode (<xref linkend="boot-singleuser"/>), the system enters multi-user mode, in which it starts the resource configuration of the system.</para> @@ -983,7 +1008,7 @@ console none <title>Shutdown Sequence</title> <indexterm> - <primary><command>shutdown</command></primary> + <primary>&man.shutdown.8;</primary> </indexterm> <para>Upon controlled shutdown using &man.shutdown.8;, @@ -997,8 +1022,8 @@ console none 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 the - <groupname>operator</groupname> group in order to run + be <username>root</username> or a member of + <groupname>operator</groupname> 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>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201305091623.r49GN2pV038934>