From owner-svn-doc-head@FreeBSD.ORG Mon Feb 4 22:21:55 2013 Return-Path: Delivered-To: svn-doc-head@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 1178CE0F; Mon, 4 Feb 2013 22:21:55 +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 0231C62A; Mon, 4 Feb 2013 22:21:55 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r14MLssb012994; Mon, 4 Feb 2013 22:21:54 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r14MLs5Z012993; Mon, 4 Feb 2013 22:21:54 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201302042221.r14MLs5Z012993@svn.freebsd.org> From: Dru Lavigne Date: Mon, 4 Feb 2013 22:21:54 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40887 - 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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 22:21:55 -0000 Author: dru Date: Mon Feb 4 22:21:54 2013 New Revision: 40887 URL: http://svnweb.freebsd.org/changeset/doc/40887 Log: This patch addresses the following: - replaces FreeBSD with &os; - rewording to replace "you" - updated the F1 example - general tightening and grammar fixes Approved by: bcr (mentor) 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 Mon Feb 4 17:32:17 2013 (r40886) +++ head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Mon Feb 4 22:21:54 2013 (r40887) @@ -6,7 +6,7 @@ --> - The FreeBSD Booting Process + The &os; Booting Process Synopsis @@ -16,31 +16,31 @@ The process of starting a computer and loading the operating system is referred to as the bootstrap process, - or simply booting. FreeBSD's boot process + or simply booting. &os;'s boot process provides a great deal of flexibility in customizing what happens - when you start the system, allowing you to select from different - operating systems installed on the same computer, or even - different versions of the same operating system or installed - kernel. - - This chapter details the configuration options you can set - and how to customize the FreeBSD boot process. This includes - everything that happens until the FreeBSD kernel has started, - probed for devices, and started &man.init.8;. If you are not - quite sure when this happens, it occurs when the text color - changes from bright white to grey. + 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. + + 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. - After reading this chapter, you will know: + After reading this chapter, you will recognize: - What the components of the FreeBSD bootstrap system are, - and how they interact. + The components of the &os; bootstrap system and how they + interact. - The options you can give to the components in the - FreeBSD bootstrap to control the boot process. + The options that can be passed to the components in the + &os; bootstrap in order to control the boot process. @@ -49,9 +49,7 @@ - x86 Only - - This chapter only describes the boot process for FreeBSD + This chapter only describes the boot process for &os; running on Intel x86 systems. @@ -62,7 +60,7 @@ 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. So if + 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? @@ -102,7 +100,7 @@ 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 - called a boot loader, but FreeBSD uses that + called a boot loader, but &os; uses that term for a later stage of booting.) Popular boot managers include boot0 (aka Boot Easy, the standard &os; boot @@ -111,30 +109,28 @@ LILO. (Only boot0 fits within the MBR.) - If you have only one operating system installed on your - disks then a standard PC MBR will suffice. This MBR searches - for the first bootable (aka active) slice on the disk, and - then runs the code on that slice to load the remainder of the - operating system. The MBR installed by &man.fdisk.8;, by - default, is such an MBR. It is based on + 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 /boot/mbr. - If you have installed multiple operating systems on your - disks then you can install a different boot manager, one that - can display a list of different operating systems, and allows - you to choose the one to boot from. Two of these are discussed - in the next subsection. + If multiple operating systems are present, a different boot + manager can be installed which displays the list of operating + 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 FreeBSD bootstrap system is divided + 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 these three stages because the PC standards put limits on - the size of the programs that can be run at stages one and two. - Chaining the tasks together allows FreeBSD to provide a more - flexible loader. + 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 init @@ -145,9 +141,8 @@ process &man.init.8;, which then makes sure the disks are in a usable state. &man.init.8; then starts the user-level resource configuration which mounts file systems, sets up network cards - to communicate on the network, and generally starts all the - processes that usually are run on a FreeBSD system at - startup. + to communicate on the network, and starts the processes which + have been configured to run on a &os; system at startup. @@ -163,60 +158,54 @@ The code in the MBR or boot manager is sometimes referred to as stage zero of the boot process. - This subsection discusses two of the boot managers previously - mentioned: boot0 and + This section discusses two boot managers: + boot0 and LILO. The <application>boot0</application> Boot Manager: - The MBR installed by FreeBSD's installer or - &man.boot0cfg.8;, by default, is based on - /boot/boot0. (The - boot0 program is very simple, - since the program in the MBR can only be - 446 bytes long because of the slice table and - 0x55AA identifier at the end of the MBR.) - If you have installed boot0 and - multiple operating systems on your hard disks, then you will - see a display similar to this one at boot - time: + 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 - F1 DOS + F1 Windows F2 FreeBSD -F3 Linux -F4 ?? -F5 Drive 1 Default: F2 - Other operating systems, in particular &windows;, have - been known to overwrite an existing MBR with their own. If - this happens to you, or you want to replace your existing MBR - with the FreeBSD MBR then use the following command: + 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: &prompt.root; fdisk -B -b /boot/boot0 device - where device is the device that - you boot from, such as ad0 for the - first IDE disk, ad2 for the first IDE - disk on a second IDE controller, da0 - for the first SCSI disk, and so on. Or, if you want a custom - configuration of the MBR, use &man.boot0cfg.8;. + 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 - FreeBSD, first start Linux and add the following to your - existing /etc/lilo.conf configuration - file: + &os;, boot into Linux and add the following to the existing + /etc/lilo.conf configuration: other=/dev/hdXY @@ -224,30 +213,29 @@ table=/dev/hdX loader=/boot/chain.b label=FreeBSD - In the above, specify FreeBSD's primary partition and - drive using Linux specifiers, replacing - X with the Linux drive letter and - Y with the Linux primary partition - number. If you are using a SCSI drive, you - will need to change /dev/hd to read - something similar to /dev/sd. The + 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 - you have both operating systems on the same drive. Now run - /sbin/lilo -v to commit your new - changes to the system; this should be verified by checking its - screen messages. + 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, <filename>/boot/boot1</filename>, and Stage Two, <filename>/boot/boot2</filename> - Conceptually the first and second stages are part of the + Conceptually, the first and second stages are part of the same program, on the same area of the disk. Because of space - constraints they have been split into two, but you would - always install them together. They are copied from the - combined file /boot/boot by the installer - or bsdlabel (see below). + 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. They are located outside file systems, in the first track of the boot slice, starting with the first sector. This is @@ -259,20 +247,18 @@ label=FreeBSD boot1 is very simple, since it can only be 512 bytes in size, and knows just enough about the - FreeBSD bsdlabel, which stores + &os; bsdlabel, which stores information about the slice, to find and execute boot2. boot2 is slightly more sophisticated, - and understands the FreeBSD file system enough to find files - on it, and can provide a simple interface to choose the kernel - or loader to run. - - Since the loader is - much more sophisticated, and provides a nice easy-to-use - boot configuration, boot2 usually runs - it, but previously it - was tasked to run the kernel directly. + and understands the &os; file system enough to find files, and + can provide a simple interface to choose the kernel or loader + to run. + + loader is much more + sophisticated and provides a boot configuration which is run + by boot2. <filename>boot2</filename> Screenshot @@ -282,25 +268,26 @@ Default: 0:ad(0,a)/boot/loader boot: - If you ever need to replace the installed - boot1 and boot2 use - &man.bsdlabel.8;: + &man.bsdlabel.8; can be used to replace the installed + boot1 and + boot2: &prompt.root; bsdlabel -B diskslice where diskslice is the disk and - slice you boot from, such as ad0s1 + slice to boot from, such as ad0s1 for the first slice on the first IDE disk. Dangerously Dedicated Mode - If you use just the disk name, such as - ad0, in the &man.bsdlabel.8; - command you will create a dangerously dedicated disk, - without slices. This is almost certainly not what you want - to do, so make sure you double check the &man.bsdlabel.8; - command before you press Return. + If just the disk name is used, such as + ad0, &man.bsdlabel.8; will create a + dangerously dedicated disk, without slices. + This is probably not the desired action, so double check the + diskslice passed to + &man.bsdlabel.8; before pressing + Return. @@ -313,16 +300,16 @@ boot: bootstrap, and is located on the file system, usually as /boot/loader. - The loader is intended as a user-friendly method for - configuration, using an easy-to-use built-in command set, - backed up by a more powerful interpreter, with a more complex - command set. + The loader is intended as an interactive method for + configuration, using a built-in command set, backed up by a + more powerful interpreter which has a more complex command + set. Loader Program Flow During initialization, the loader will probe for a - console and for disks, and figure out what disk it is + 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. @@ -342,16 +329,16 @@ boot: 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 easy-to-use command set, where - the user may adjust variables, unload all modules, load - modules, and then finally boot or reboot. + 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 These are the most commonly used loader commands. For a - complete discussion of all available commands, please see + complete discussion of all available commands, refer to &man.loader.8;. @@ -372,11 +359,10 @@ boot: kernelname - Immediately proceeds to boot the kernel, with the - given options, if any, and with the kernel name given, - if it is. Providing a kernel name on the command-line - is only applicable after an - unload command has been issued, + Immediately proceeds to boot the kernel, with any + specified options or kernel name. Providing a kernel + name on the command-line is only applicable after an + unload command has been issued; otherwise the previously-loaded kernel will be used. @@ -387,10 +373,10 @@ boot: Goes through the same automatic configuration of - modules based on variables as what happens at boot. - This only makes sense if you use - unload first, and change some - variables, most commonly kernel. + modules based on specified variables, most commonly + kernel. This only makes sense if + unload is used first, before + changing some variables. @@ -401,8 +387,8 @@ boot: Shows help messages read from /boot/loader.help. If the topic - given is index, then the list of - available topics is given. + given is index, the list of + available topics is displayed. @@ -412,7 +398,7 @@ boot: Processes the file with the given filename. The - file is read in, and interpreted line by line. An + file is read in and interpreted line by line. An error immediately stops the include command. @@ -424,8 +410,9 @@ boot: Loads the kernel, kernel module, or file of the - type given, with the filename given. Any arguments - after filename are passed to the file. + type given, with the specified filename. Any + arguments after filename + are passed to the file. @@ -436,8 +423,8 @@ boot: Displays a listing of files in the given path, or the root directory, if the path is not specified. If - is specified, file sizes will be - shown too. + is specified, file sizes will + also be shown. @@ -508,15 +495,14 @@ boot: single-user mode - To boot your usual kernel, but in single-user - mode: + To boot the usual kernel in single-user mode: boot -s - To unload your usual kernel and modules, and then - load just your old (or another) kernel: + To unload the usual kernel and modules, and then + load the previous or another kernel: kernel.old @@ -525,14 +511,14 @@ boot: unload load kernel.old - You can use kernel.GENERIC to - refer to the generic kernel that comes on the install - disk, or kernel.old to refer to - your previously installed kernel (when you have upgraded - or configured your own kernel, for example). + Use kernel.GENERIC to refer to + the default kernel that comes with an installation, or + kernel.old to refer to the + previously installed kernel before a system upgrade or + before configuring a custom kernel. - Use the following to load your usual modules with + Use the following to load the usual modules with another kernel: unload @@ -541,9 +527,8 @@ boot: - To load a kernel configuration script (an automated - script which does the things you would normally do in - the kernel boot-time configurator): + To load an automated kernel configuration + script: load -t userconfig_script /boot/kernel.conf @@ -563,89 +548,58 @@ boot: Boot Time Splash Screens - The splash screen creates a more visually appealing boot - screen compared to the original boot messages. This screen - will be displayed until a console login prompt or an X - display manager offers a login prompt. + 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 - X11 Desktop graphical environment. After - X11 and one of the - graphical - desktop environments, such as - GNOME, - KDE, or - XFce are installed, the X11 - desktop can be launched by using - startx. - - Some users prefer the X11 graphical login screen over - the traditional text based login prompt. Display managers - like XDM for &xorg;, - gdm for - GNOME, and - kdm for - KDE (and any other from the Ports - Collection) provide a graphical login screen in - place of the console login prompt. After a successful - login, they present the user with a graphical - desktop. - - In the command line environment, the splash screen would - hide all the boot probe messages and task startup messages - before displaying the login prompt. In X11 environment, the - users would get a visually clearer system start up - experience resembling something closer to what a - (µsoft; &windows; or non-unix type system) user would - experience. + graphical environment provided by + Xorg. 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 - The splash screen function supports 256-color + The splash screen function supports 256-colors in the bitmap (.bmp), ZSoft PCX (.pcx), or - TheDraw (.bin) files. - In addition, the splash image files must have a resolution - of 320 by 200 pixels or less to work on standard VGA - adapters. + 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, activate the VESA - support included in &os;. This can be enabled by loading - the VESA module during system boot, or - adding a VESA kernel configuration - option and building a custom kernel (see ). The VESA - support gives users the ability to display a splash screen - image that fills the whole display screen. + 1024 by 768 pixels, load the VESA + module during system boot. For a custom kernel, 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 of X11. After a time period of non-use the - screen will change to the splash screen and cycle through - steps of changing intensity of the image, from bright to a - very dark and over again. This default splash screen - (screen saver) behavior could be overridden by adding a + 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. Option - saver= has several built-in screen - savers to choose from, the full list can be found in the - &man.splash.4; manual page. The default screen saver is - called warp. Note that the - saver= option specified in - /etc/rc.conf only applies to virtual - consoles. It has no effect on X11 display - managers. + /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 + 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 @@ -660,15 +614,14 @@ boot: Enabling the Splash Screen Function - The splash screen (.bmp, - .pcx, or .bin) - file has to be placed on the root partition, for example - in the /boot - directory. - - For default boot display resolution (256-color, 320 by - 200 pixels, or less), edit - /boot/loader.conf, so it contains the + 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" @@ -685,19 +638,19 @@ splash_bmp_load="YES" bitmap_load="YES" bitmap_name="/boot/splash.bmp" - The above assumes that + This example assumes that /boot/splash.bmp - is used for splash screen. When a PCX - file is desired, use the following statements, plus the - vesa_load="YES" line depending on the - resolution. + 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" bitmap_load="YES" bitmap_name="/boot/splash.pcx" - In version 8.3 another option is to use ascii art in - Beginning with &os; 8.3, another option is to use + ASCII art in TheDraw format. @@ -707,14 +660,14 @@ bitmap_name="/boot/splash.b 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 above types - such as, + can be anything as long as it is one of the supported + types such as, splash_640x400.bmp or bluewave.pcx. - Some other interesting - loader.conf options: + Other interesting + loader.conf options include: @@ -737,13 +690,13 @@ bitmap_name="/boot/splash.b This will replace the default words &os;, which are displayed to the right of the boot options menu with the colored - beastie logo like releases in the past had. + beastie logo. - For more information, please see the &man.splash.4;, - &man.loader.conf.5;, and &man.vga.4; manual pages. + For more information, refer to &man.splash.4;, + &man.loader.conf.5;, and &man.vga.4;. @@ -757,10 +710,10 @@ bitmap_name="/boot/splash.b boot interaction - Once the kernel is loaded by either loader (as usual) or boot2 (bypassing 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 its boot flags, if any, and adjusts its behavior as necessary. @@ -778,7 +731,7 @@ bitmap_name="/boot/splash.b - during kernel initialization, ask for the device + During kernel initialization, ask for the device to mount as the root file system. @@ -787,7 +740,7 @@ bitmap_name="/boot/splash.b - boot from CDROM. + Boot from CDROM. @@ -795,8 +748,8 @@ bitmap_name="/boot/splash.b - run UserConfig, the boot-time kernel - configurator + Run UserConfig, the boot-time kernel + configurator. @@ -804,7 +757,7 @@ bitmap_name="/boot/splash.b - boot into single-user mode + Boot into single-user mode. @@ -812,14 +765,14 @@ bitmap_name="/boot/splash.b - be more verbose during kernel startup + Be more verbose during kernel startup. - There are other boot flags, read &man.boot.8; for more - information on them. + Refer to &man.boot.8; for more information on the other + boot flags. @@ -848,27 +801,26 @@ bitmap_name="/boot/splash.b device.hints - During initial system startup, the boot &man.loader.8; will - read the &man.device.hints.5; file. This file stores kernel - boot information known as variables, sometimes referred to as + During initial system startup, the boot &man.loader.8; reads + &man.device.hints.5;. This file stores kernel boot information + known as variables, sometimes referred to as 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. Variables can be added using - set, removed with unset, - and viewed with the show commands. Variables - set in /boot/device.hints can be - overridden here also. Device hints entered at the boot loader - are not permanent and will be forgotten on the next - reboot. + Device hints may also be specified at the Stage 3 boot loader prompt. + Variables can be added using set, removed + with unset, and viewed + show. Variables set in + /boot/device.hints can also be overridden. + Device hints entered at the boot loader are not permanent and + will not be applied on the next reboot. - Once the system is booted, the &man.kenv.1; command can be - used to dump all of the variables. + Once the system is booted, &man.kenv.1; can be used to dump + all of the variables. The syntax for /boot/device.hints - is one variable per line, using the standard hash + is one variable per line, using the hash # as comment markers. Lines are constructed as follows: @@ -878,7 +830,7 @@ bitmap_name="/boot/splash.b set hint.driver.unit.keyword=value - driver is the device driver name, + where driver is the device driver name, unit is the device driver unit number, and keyword is the hint keyword. The keyword may consist of the following options: @@ -920,10 +872,10 @@ bitmap_name="/boot/splash.b - Device drivers may accept (or require) more hints not listed - here, viewing their manual page is recommended. For more - information, consult the &man.device.hints.5;, &man.kenv.1;, - &man.loader.conf.5;, and &man.loader.8; manual pages. + Since device drivers may accept or require more hints not + listed here, viewing a driver's manual page is recommended. + For more information, refer to &man.device.hints.5;, + &man.kenv.1;, &man.loader.conf.5;, and &man.loader.8;. @@ -944,10 +896,10 @@ 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, - &man.init.8; drops the system into - single-user mode for - the system administrator to take care of the problems + 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. @@ -957,21 +909,19 @@ bitmap_name="/boot/splash.b single-user mode console - This mode can be reached through the - automatic reboot - sequence, or by the user booting with the - option or setting the - boot_single variable in + This mode can be reached through the automatic reboot sequence, + the user booting with , or by setting + the boot_single variable in loader. - It can also be reached by calling &man.shutdown.8; without - the reboot () or halt () - options, from multi-user - mode. + It can also be reached by calling &man.shutdown.8; from + multi-user mode without + including or . If the system console is set to insecure in /etc/ttys, - then the system prompts for the root + the system will prompt for the root password before initiating single-user mode. @@ -986,13 +936,12 @@ console none - An insecure console means that you - consider your physical security to the console to be - insecure, and want to make sure only someone who knows the - root password may use single-user mode, - and it does not mean that you want to run your console - insecurely. Thus, if you want security, choose - insecure, not + 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. @@ -1002,8 +951,8 @@ console none multi-user mode - If &man.init.8; finds your file systems to be in order, or - once the user has finished in 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. @@ -1018,14 +967,13 @@ console none /etc/defaults/rc.conf, and system-specific details from /etc/rc.conf, and then proceeds to - mount the system file systems mentioned in - /etc/fstab, start up networking - services, start up miscellaneous system daemons, and - finally runs the startup scripts of locally installed - packages. + 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 &man.rc.8; manual page is a good reference to the - resource configuration system, as is examining the scripts + To learn more about the resource configuration system, + refer to &man.rc.8; and examine the scripts themselves. @@ -1038,27 +986,26 @@ console none shutdown - Upon controlled shutdown, via &man.shutdown.8;, + Upon controlled shutdown using &man.shutdown.8;, &man.init.8; will attempt to run the script /etc/rc.shutdown, and then proceed to send all processes the TERM signal, and subsequently the KILL signal to any that do - not terminate timely. + not terminate in a timely manner. - To power down a FreeBSD machine on architectures and systems - that support power management, use the command - shutdown -p now to turn the power off - immediately. To just reboot a FreeBSD system, just use - shutdown -r now. You need to be - root or a member of - operator group to run &man.shutdown.8;. - The &man.halt.8; and &man.reboot.8; commands can also be used, - please refer to their manual pages and to &man.shutdown.8;'s one - for more information. + To power down a &os; machine on architectures and systems + 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 + &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. - Power management requires &man.acpi.4; support in the - kernel or loaded as module for. + Power management requires &man.acpi.4; to be loaded as + a module or staticly compiled into a custom kernel.