From owner-svn-doc-projects@FreeBSD.ORG Thu May 9 16:23:02 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9E5E3B1F; Thu, 9 May 2013 16:23:02 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 7F7B7FF4; Thu, 9 May 2013 16:23:02 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r49GN2Zb038935; Thu, 9 May 2013 16:23:02 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r49GN2pV038934; Thu, 9 May 2013 16:23:02 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201305091623.r49GN2pV038934@svn.freebsd.org> From: Dru Lavigne Date: Thu, 9 May 2013 16:23:02 +0000 (UTC) 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 X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 May 2013 16:23:02 -0000 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 booting. - BIOS + BIOS Basic Input/Output System - BIOS + BIOS - On x86 hardware the Basic Input/Output System (BIOS) is + On x86 hardware the Basic Input/Output System + (BIOS) 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 + 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 loading the operating system, possibly with the help of the - BIOS. + BIOS. - Master Boot Record (MBR) + Master Boot Record + MBR) Boot Manager Boot Loader - The code within the MBR is usually referred to as a + The code within the MBR is usually + referred to as a boot manager, 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 track 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 boot loader, but &os; uses that - term for a later stage of booting.) Popular boot managers - include boot0 (aka + term for a later stage of booting. Popular boot managers + include boot0, also called Boot Easy, the standard &os; boot - manager), Grub, + manager, Grub, GAG, and - LILO. (Only - boot0 fits within the MBR.) - - If only one operating system is installed, a standard PC MBR - will suffice. This MBR searches for the first bootable (active) + LILO. Only + boot0 fits within the + MBR. + + If only one operating system is installed, a standard PC + MBR + will suffice. This MBR 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 + MBR + installed by &man.fdisk.8; is such an MBR and + is based on /boot/mbr. If multiple operating systems are present, a different boot @@ -122,7 +135,8 @@ boot managers are discussed in the next subsection. 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 + MBR, 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. kernel - init + &man.init.8; 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 @@ The Boot Manager Master Boot Record - (MBR) + (MBR) - The code in the MBR or boot manager is sometimes referred + The code in the MBR or boot manager is + sometimes referred to as stage zero of the boot process. This section discusses two boot managers: boot0 and @@ -166,12 +181,13 @@ The <application>boot0</application> Boot Manager: - The MBR installed by &os;'s installer or + The MBR installed by &os;'s installer + or &man.boot0cfg.8; is based on /boot/boot0. The size and capability of boot0 is restricted to 446 bytes due to the slice table and 0x55AA - identifier at the end of the MBR. If + identifier at the end of the MBR. If boot0 and multiple operating systems are installed, a message similar to this example will be displayed at boot time: @@ -187,18 +203,25 @@ Default: F2 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: + overwrite an existing MBR if they are + installed after &os;. + If this happens, or to replace the existing + MBR + with the &os; MBR, use the following + command: &prompt.root; fdisk -B -b /boot/boot0 device where device is the boot disk, - such as ad0 for the first IDE disk, - ad2 for the first IDE disk on a - second IDE controller, or da0 - for the first SCSI disk. To create a custom configuration of - the MBR, refer to &man.boot0cfg.8;. + such as ad0 for the first + IDE disk, + ad2 for the first + IDE disk on a + second IDE controller, or + da0 + for the first SCSI disk. To create a + custom configuration of + the MBR, refer to &man.boot0cfg.8;. The LILO Boot Manager: @@ -235,11 +258,11 @@ label=FreeBSD constraints, they have been split into two, but are always installed together. They are copied from the combined /boot/boot by the installer or - bsdlabel. + &man.bsdlabel.8;. They are located outside file systems, in the first track of the boot slice, starting with the first sector. This is - where boot0, or any other + where 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 can provide a simple interface to choose the kernel or loader to run. - loader is much more + However, &man.loader.8; is much more sophisticated and provides a boot configuration which is run by boot2. @@ -276,7 +299,8 @@ boot: where diskslice is the disk and slice to boot from, such as ad0s1 - for the first slice on the first IDE disk. + for the first slice on the first IDE + disk. Dangerously Dedicated Mode @@ -557,8 +581,8 @@ boot: 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 - Xorg. Refer to that chapter for + graphical environment as described in + . Refer to that chapter for more information on how to install and configure a graphical display manager and a graphical login manager. @@ -574,8 +598,8 @@ boot: To use larger images, up to the maximum resolution of 1024 by 768 pixels, load the VESA - module during system boot. For a custom kernel, include the + module during system boot. For a custom kernel, as + described in , include the VESA kernel configuration option. Loading VESA support provides the ability to display a splash screen image that fills the @@ -710,10 +734,10 @@ bitmap_name="/boot/splash.b boot interaction - Once the kernel is loaded by either the default loader or by boot2 which bypasses the loader, - it examines its boot flags, if any, and adjusts its behavior as + 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. @@ -807,8 +831,9 @@ bitmap_name="/boot/splash.b device hints. These device hints are used by device drivers for device configuration. - Device hints may also be specified at the Stage 3 boot loader prompt. + Device hints may also be specified at the Stage 3 boot + loader prompt, as demonstrated in . Variables can be added using set, removed with unset, and viewed show. Variables set in @@ -882,7 +907,7 @@ bitmap_name="/boot/splash.b Init: Process Control Initialization - init + &man.init.8; Once the kernel has finished booting, it passes control to @@ -897,8 +922,8 @@ bitmap_name="/boot/splash.b 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 - single-user mode so + file system, &man.init.8; drops the system into single-user + mode () so that the system administrator can resolve the problem directly. @@ -909,14 +934,14 @@ bitmap_name="/boot/splash.b single-user mode console - This mode can be reached through the automatic reboot sequence, + This mode can be reached through the automatic reboot + sequence (), the user booting with , or by setting the boot_single variable in - loader. + &man.loader.8;. It can also be reached by calling &man.shutdown.8; from - multi-user mode without + multi-user mode () without including or . If the system console is set to @@ -952,8 +977,8 @@ console none multi-user mode If &man.init.8; finds the file systems to be in order, or - once the user has finished their commands in single-user mode, the + once the user has finished their commands in single-user + mode (), the system enters multi-user mode, in which it starts the resource configuration of the system. @@ -983,7 +1008,7 @@ console none Shutdown Sequence - shutdown + &man.shutdown.8; Upon controlled shutdown using &man.shutdown.8;, @@ -997,8 +1022,8 @@ console none that support power management, use shutdown -p now to turn the power off immediately. To reboot a &os; system, use shutdown -r now. One must - be root or a member of the - operator group in order to run + be root or a member of + operator 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.