From owner-svn-doc-projects@FreeBSD.ORG Thu May 9 20:54:52 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 39F61157; Thu, 9 May 2013 20:54:52 +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 2945F147; Thu, 9 May 2013 20:54:52 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r49Ksq7P036208; Thu, 9 May 2013 20:54:52 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r49Ksq3D036207; Thu, 9 May 2013 20:54:52 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201305092054.r49Ksq3D036207@svn.freebsd.org> From: Dru Lavigne Date: Thu, 9 May 2013 20:54:52 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41583 - 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 20:54:52 -0000 Author: dru Date: Thu May 9 20:54:51 2013 New Revision: 41583 URL: http://svnweb.freebsd.org/changeset/doc/41583 Log: White space fix only. Translators can ignore. 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 20:51:46 2013 (r41582) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/boot/chapter.xml Thu May 9 20:54:51 2013 (r41583) @@ -16,9 +16,9 @@ The process of starting a computer and loading the operating system is referred to as the bootstrap process, - or simply booting. &os;'s boot process - provides a great deal of flexibility in customizing what happens - when the system starts, including the ability to select from + or simply booting. &os;'s boot process provides + a great deal of flexibility in customizing what happens when + the system starts, including the ability to select from different operating systems installed on the same computer, different versions of the same operating system, or a different installed kernel. @@ -81,18 +81,15 @@ 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 - loading the operating system, possibly with the help of the - BIOS. + (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 loading the operating system, + possibly with the help of the BIOS. Master Boot Record MBR) @@ -102,14 +99,13 @@ Boot Loader 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 - code in the first track of the disk or - 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 + referred to as a boot manager, especially + when it interacts with the user. In this case, the boot + manager usually has more code in the first + track of the disk or 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, also called Boot Easy, the standard &os; boot manager, Grub, @@ -119,14 +115,12 @@ MBR. If only one operating system is installed, a standard PC - MBR - will suffice. This MBR searches for the - first bootable (active) + 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 + 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 @@ -136,15 +130,14 @@ The remainder of the &os; bootstrap system is divided 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 - the task of loading the operating system. The work is split - into three stages because PC standards put limits on the size of - the programs that can be run at stages one and two. Chaining - the tasks together allows &os; to provide a more flexible - loader. + 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 the task of loading the + operating system. The work is split into three stages because + PC standards put limits on the size of the programs that can + be run at stages one and two. Chaining the tasks together + allows &os; to provide a more flexible loader. kernel &man.init.8; @@ -171,9 +164,8 @@ (MBR) 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: + sometimes referred to as stage zero of + the boot process. This section discusses two boot managers: boot0 and LILO. @@ -182,8 +174,7 @@ Manager: The MBR installed by &os;'s installer - or - &man.boot0cfg.8; is based on + 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 @@ -204,24 +195,21 @@ Default: F2 Other operating systems, in particular &windows;, will 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: + 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 + 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;. + custom configuration of the MBR, refer to + &man.boot0cfg.8;. The LILO Boot Manager: @@ -279,9 +267,9 @@ label=FreeBSD can provide a simple interface to choose the kernel or loader to run. - However, &man.loader.8; is much more - sophisticated and provides a boot configuration which is run - by boot2. + However, &man.loader.8; is much more sophisticated and + provides a boot configuration which is run by + boot2. <filename>boot2</filename> Screenshot @@ -581,10 +569,10 @@ 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 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. + 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. Splash Screen Function @@ -690,8 +678,8 @@ bitmap_name="/boot/splash.b or bluewave.pcx. - Other interesting - loader.conf options include: + Other interesting loader.conf + options include: @@ -736,8 +724,8 @@ bitmap_name="/boot/splash.b 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 + linkend="boot-boot1"/>), which bypasses the loader, it + examines any boot flags and adjusts its behavior as necessary. @@ -923,9 +911,8 @@ bitmap_name="/boot/splash.b 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 - that the system administrator can resolve the problem - directly. + mode () so that the system + administrator can resolve the problem directly. @@ -935,10 +922,9 @@ bitmap_name="/boot/splash.b console This mode can be reached through the automatic reboot - sequence (), - the user booting with , or by setting - the boot_single variable in - &man.loader.8;. + sequence (), the user booting + with , or by setting the boot_ + single variable in &man.loader.8;. It can also be reached by calling &man.shutdown.8; from multi-user mode () without @@ -978,9 +964,9 @@ console none 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 - system enters multi-user mode, in which it starts the - resource configuration of the system. + mode (), the system enters + multi-user mode, in which it starts the resource configuration + of the system. Resource Configuration (rc)