From owner-svn-doc-all@FreeBSD.ORG Fri Apr 18 20:31:05 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0A2F82CC; Fri, 18 Apr 2014 20:31:05 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EA9071C02; Fri, 18 Apr 2014 20:31:04 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s3IKV4YP036972; Fri, 18 Apr 2014 20:31:04 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s3IKV4SN036971; Fri, 18 Apr 2014 20:31:04 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201404182031.s3IKV4SN036971@svn.freebsd.org> From: Dru Lavigne Date: Fri, 18 Apr 2014 20:31:04 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44609 - head/en_US.ISO8859-1/books/handbook/boot X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Apr 2014 20:31:05 -0000 Author: dru Date: Fri Apr 18 20:31:04 2014 New Revision: 44609 URL: http://svnweb.freebsd.org/changeset/doc/44609 Log: White space fix only. Translators can ignore. 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 Fri Apr 18 19:59:56 2014 (r44608) +++ head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Fri Apr 18 20:31:04 2014 (r44609) @@ -26,10 +26,10 @@ different versions of the same operating system, or a different installed kernel. - This chapter details the configuration options that can - be set. It demonstrates how to customize the &os; boot - process, including everything that happens until the &os; kernel - has started, probed for devices, and started &man.init.8;. This + This chapter details the configuration options that can be + set. It demonstrates how to customize the &os; boot process, + including everything that happens until the &os; kernel has + started, probed for devices, and started &man.init.8;. This occurs when the text color of the boot messages changes from bright white to grey. @@ -63,8 +63,8 @@ Turning on a computer and starting the operating system poses an interesting dilemma. By definition, the computer does not know how to do anything until the operating system is - started. This includes running programs from the disk. If - the computer can not run a program from the disk without the + started. This includes running programs from the disk. If the + computer can not run a program from the disk without the operating system, and the operating system programs are on the disk, how is the operating system started? @@ -129,16 +129,16 @@ systems so that the user can choose which one to boot from. Two 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 + 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 + 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. + 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; @@ -158,85 +158,83 @@ Boot Manager - Master Boot Record - (MBR) + Master Boot Record + (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: - boot0 and - LILO. - - - The <application>boot0</application> Boot - Manager: - - 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 - boot0 and multiple operating - systems are installed, a message similar to this example - will be displayed at boot time: - + 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 + LILO. + + + The <application>boot0</application> Boot + Manager: + + 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 + boot0 and multiple operating + systems are installed, a message similar to this example will + be displayed at boot time: + - - <filename>boot0</filename> Screenshot + + <filename>boot0</filename> Screenshot - F1 Win + F1 Win F2 FreeBSD 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: - - &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;. - - - The LILO Boot Manager: - - To install this boot manager so it will also boot - &os;, boot into Linux and add the following to the existing - /etc/lilo.conf configuration: - + 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: + + &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;. + + + The LILO Boot Manager: + + To install this boot manager so it will also boot &os;, + boot into Linux and add the following to the existing + /etc/lilo.conf configuration: + - other=/dev/hdXY + other=/dev/hdXY table=/dev/hdX loader=/boot/chain.b label=FreeBSD - Specify &os;'s primary partition and drive using Linux - specifiers, replacing X with the - Linux drive letter and Y with the - Linux primary partition number. For a SCSI - drive, change /dev/hd to - /dev/sd. The - line can be omitted if - both operating systems are installed on the same drive. Next, - run /sbin/lilo -v to commit the new - changes. Verify these are correct by checking the screen - messages. + Specify &os;'s primary partition and drive using Linux + specifiers, replacing X with the + Linux drive letter and Y with the + Linux primary partition number. For a SCSI + drive, change /dev/hd to + /dev/sd. The + line can be omitted if + both operating systems are installed on the same drive. Next, + run /sbin/lilo -v to commit the new + changes. Verify these are correct by checking the screen + messages. - Stage One and Stage - Two + Stage One and Stage Two Conceptually, the first and second stages are part of the same program, on the same area of the disk. Because of space @@ -314,30 +312,30 @@ boot: more powerful interpreter which has a more complex command set. - 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 - interpreter is started where user commands can be passed - from a script or interactively. - - loader - loader configuration - - The loader will then read - /boot/loader.rc, which by default reads - in /boot/defaults/loader.conf which - sets reasonable defaults for variables and reads - /boot/loader.conf for local changes to - those variables. loader.rc then acts - on these variables, loading whichever modules and kernel are - selected. - - Finally, by default, the loader issues a 10 second wait - for key presses, and boots the kernel if it is not - interrupted. If interrupted, the user is presented with a - prompt which understands the command set, where the user may - adjust variables, unload all modules, load modules, and then - finally boot or reboot. + 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 + interpreter is started where user commands can be passed from + a script or interactively. + + loader + loader configuration + + The loader will then read + /boot/loader.rc, which by default reads + in /boot/defaults/loader.conf which sets + reasonable defaults for variables and reads + /boot/loader.conf for local changes to + those variables. loader.rc then acts on + these variables, loading whichever modules and kernel are + selected. + + Finally, by default, the loader issues a 10 second wait + for key presses, and boots the kernel if it is not + interrupted. If interrupted, the user is presented with a + prompt which understands the command set, where the user may + adjust variables, unload all modules, load modules, and then + finally boot or reboot. Loader Built-In Commands @@ -539,19 +537,17 @@ boot: - - Kernel Interaction During Boot + + Kernel Interaction During Boot - - kernel - boot interaction - + + kernel + boot interaction + - 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. + 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. kernel @@ -610,15 +606,16 @@ boot: - - - - Configuring Boot Time Splash Screens + + + Configuring Boot Time Splash Screens @@ -629,150 +626,146 @@ boot: Contributed by - + - The splash screen creates an alternate boot screen. The - splash screen hides all the boot probe messages and service - startup messages before displaying either a command line or - graphical login prompt. - - There are two basic environments available in &os;. The - 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. - - The splash screen function supports 256-colors in the - bitmap (.bmp), ZSoft - PCX (.pcx), or - TheDraw (.bin) formats. The splash - image files must have a resolution of 320 by 200 pixels or - less in order to work on standard VGA adapters. - - 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, as - described in , include the - VESA kernel configuration option. - Loading VESA support provides the - ability to display a splash screen image that fills the - whole display screen. - - While the splash screen is being displayed during the - booting process, it can be turned off any time by hitting - any key on the keyboard. - - The splash screen also defaults to being a screen - saver outside. After a time period of non-use, the splash - screen will be displayed and will cycle through steps of - changing intensity of the image, from bright to very dark - and over again. The configuration of the splash screen - saver can be overridden by adding a - saver= line to - /etc/rc.conf. Several built-in - screen savers are available and described in - &man.splash.4;. The saver= option only - applies to virtual consoles and has no effect on graphical - display managers. - - A few boot loader messages, including the boot options - menu and a timed wait count down prompt, are displayed at - boot time, even when the splash screen is enabled. - - Sample splash screen files can be downloaded from the - gallery at http://artwork.freebsdgr.org. - By installing the - sysutils/bsd-splash-changer port, - splash images can be chosen from a collection randomly at - each boot. - - The splash screen .bmp, - .pcx, or .bin - image has to be placed on the root partition, for example - in /boot. - - For the default boot display resolution of 256-colors - and 320 by 200 pixels or less, edit - /boot/loader.conf so it contains the - following: + The splash screen creates an alternate boot screen. The + splash screen hides all the boot probe messages and service + startup messages before displaying either a command line or + graphical login prompt. + + There are two basic environments available in &os;. The + 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. + + The splash screen function supports 256-colors in the + bitmap (.bmp), ZSoft + PCX (.pcx), or + TheDraw (.bin) formats. The splash image + files must have a resolution of 320 by 200 pixels or less in + order to work on standard VGA adapters. + + 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, as described in + , include the + VESA kernel configuration option. Loading + VESA support provides the ability to + display a splash screen image that fills the whole display + screen. + + While the splash screen is being displayed during the + booting process, it can be turned off any time by hitting any + key on the keyboard. + + The splash screen also defaults to being a screen saver + outside. After a time period of non-use, the splash screen + will be displayed and will cycle through steps of changing + intensity of the image, from bright to very dark and over + again. The configuration of the splash screen saver can be + overridden by adding a saver= line to + /etc/rc.conf. Several built-in screen + savers are available and described in &man.splash.4;. The + saver= option only applies to virtual + consoles and has no effect on graphical display + managers. + + A few boot loader messages, including the boot options + menu and a timed wait count down prompt, are displayed at + boot time, even when the splash screen is enabled. + + Sample splash screen files can be downloaded from the + gallery at http://artwork.freebsdgr.org. + By installing the + sysutils/bsd-splash-changer port, splash + images can be chosen from a collection randomly at each + boot. + + The splash screen .bmp, + .pcx, or .bin image + has to be placed on the root partition, for example in + /boot. + + For the default boot display resolution of 256-colors and + 320 by 200 pixels or less, edit + /boot/loader.conf so it contains the + following: - splash_bmp_load="YES" + splash_bmp_load="YES" bitmap_load="YES" bitmap_name="/boot/splash.bmp" - For larger video resolutions up to the maximum of 1024 - by 768 pixels, edit - /boot/loader.conf, so it contains the - following: + For larger video resolutions up to the maximum of 1024 by + 768 pixels, edit /boot/loader.conf, so it + contains the following: - vesa_load="YES" + vesa_load="YES" splash_bmp_load="YES" bitmap_load="YES" bitmap_name="/boot/splash.bmp" - This example assumes that - /boot/splash.bmp - is used for the splash screen. To use a - PCX file, use the following statements, - plus the vesa_load="YES" line, - depending on the resolution: + This example assumes that + /boot/splash.bmp + is used for the splash screen. To use a + PCX file, use the following statements, + plus the vesa_load="YES" line, depending on + the resolution: - splash_pcx_load="YES" + splash_pcx_load="YES" bitmap_load="YES" bitmap_name="/boot/splash.pcx" - Beginning with &os; 8.3, another option is to use - ASCII art in TheDraw - format. + Beginning with &os; 8.3, another option is to use + ASCII art in TheDraw + format. - splash_txt="YES" + splash_txt="YES" bitmap_load="YES" bitmap_name="/boot/splash.bin" - The file name is not restricted to - splash as shown in the above example. It - can be anything as long as it is one of the supported - types such as, - splash_640x400.bmp - or - bluewave.pcx. - - Other interesting loader.conf - options include: - - - - beastie_disable="YES" - - - This will stop the boot options menu from being - displayed, but the timed wait count down prompt will - still be present. Even with the display of the boot - options menu disabled, entering an option selection - at the timed wait count down prompt will enact the - corresponding boot option. - - - - - loader_logo="beastie" - - - This will replace the default words - &os;, which are displayed to the - right of the boot options menu with the colored - beastie logo. - - - + The file name is not restricted to splash + as shown in the above example. It can be anything as long as + it is one of the supported types such as, + splash_640x400.bmp + or + bluewave.pcx. + + Other interesting loader.conf options + include: + + + beastie_disable="YES" - For more information, refer to &man.splash.4;, - &man.loader.conf.5;, and &man.vga.4;. + + This will stop the boot options menu from being + displayed, but the timed wait count down prompt will + still be present. Even with the display of the boot + options menu disabled, entering an option selection at + the timed wait count down prompt will enact the + corresponding boot option. + + + + + loader_logo="beastie" + + + This will replace the default words + &os;, which are displayed to the right of + the boot options menu with the colored beastie + logo. + + + + + For more information, refer to &man.splash.4;, + &man.loader.conf.5;, and &man.vga.4;. @@ -885,12 +878,11 @@ bitmap_name="/boot/splash.b in the init_path variable in loader. - 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 so that the system - administrator can resolve the problem directly. + 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 so that the + system administrator can resolve the problem directly. Single-User Mode @@ -899,9 +891,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 @@ -909,8 +901,8 @@ bitmap_name="/boot/splash.b If the system console is set to insecure in /etc/ttys, - the system will prompt for the - root password before + the system will prompt for the root password before initiating single-user mode. @@ -927,11 +919,11 @@ console none An insecure console means that physical security to the console is considered to be - insecure, so only someone who knows the - root password may - use single-user mode. Thus, to add this measure of - security, choose insecure, instead of the - default of secure. + insecure, so only someone who knows the root password may use + single-user mode. Thus, to add this measure of security, + choose insecure, instead of the default + of secure. @@ -941,26 +933,24 @@ 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 system enters + 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. - rc files + rc files + + The resource configuration system reads in configuration + defaults from /etc/defaults/rc.conf, and + system-specific details from + /etc/rc.conf, and then proceeds to mount + the system file systems listed in + /etc/fstab. It starts up networking + services, miscellaneous system daemons, then the startup + scripts of locally installed packages. - The resource configuration system reads in - configuration defaults from - /etc/defaults/rc.conf, and - system-specific details from - /etc/rc.conf, and then proceeds to - mount the system file systems listed in - /etc/fstab. It starts up networking - services, miscellaneous system daemons, then the startup - scripts of locally installed packages. - - To learn more about the resource configuration system, - refer to &man.rc.8; and examine the scripts - themselves. + To learn more about the resource configuration system, + refer to &man.rc.8; and examine the scripts themselves.