12.3. The Boot Manager and Boot Stages

12.3. The Boot Manager and Boot Stages
Poprzedni	Rozdział 12. The FreeBSD Booting Process	Następny

12.3.1. The Boot Manager

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 LILO.

The boot0 Boot Manager: The MBR installed by FreeBSD's installer or 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:

Przykład 12.1. boot0 Screenshot

F1 DOS
F2 FreeBSD
F3 Linux
F4 ??
F5 Drive 1

Default: F2

Other operating systems, in particular Windows(R), 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:

# 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 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:

other=/dev/hdXY
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 loader=/boot/chain.b 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.

12.3.2. Stage One, `/boot/boot1`, and Stage Two, `/boot/boot2`

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).

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 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 /boot/boot.

boot1 is very simple, since it can only be 512 bytes in size, and knows just enough about the FreeBSD 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.

Przykład 12.2. boot2 Screenshot

>> FreeBSD/i386 BOOT
Default: 0:ad(0,a)/boot/loader
boot:

If you ever need to replace the installed boot1 and boot2 use bsdlabel(8):

# bsdlabel -B diskslice

where diskslice is the disk and slice you 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 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 bsdlabel(8) command before you press Return.

12.3.3. Stage Three, `/boot/loader`

The loader is the final stage of the three-stage 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.

12.3.3.1. Loader Program Flow

During initialization, the loader will probe for a console and for disks, and figure out what 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.

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 easy-to-use command set, where the user may adjust variables, unload all modules, load modules, and then finally boot or reboot.

12.3.3.2. Loader Built-In Commands

These are the most commonly used loader commands. For a complete discussion of all available commands, please see loader(8).

autoboot seconds: Proceeds to boot the kernel if not interrupted within the time span given, in seconds. It displays a countdown, and the default time span is 10 seconds.
boot [-options] [kernelname]: Immediately proceeds to boot the kernel, with the given options, if any, and with the kernel name given, if it is.
boot-conf: 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.
help [topic]: Shows help messages read from /boot/loader.help. If the topic given is index, then the list of available topics is given.
include filename ...: Processes the file with the given filename. The file is read in, and interpreted line by line. An error immediately stops the include command.
load [-t type] filename: Loads the kernel, kernel module, or file of the type given, with the filename given. Any arguments after filename are passed to the file.
ls [-l] [path]: Displays a listing of files in the given path, or the root directory, if the path is not specified. If -l is specified, file sizes will be shown too.
lsdev [-v]: Lists all of the devices from which it may be possible to load modules. If -v is specified, more details are printed.
lsmod [-v]: Displays loaded modules. If -v is specified, more details are shown.
more filename: Displays the files specified, with a pause at each LINES displayed.
reboot: Immediately reboots the system.
set variable, set variable=value: Sets the loader's environment variables.
unload: Removes all loaded modules.

12.3.3.3. Loader Examples

Here are some practical examples of loader usage:

To simply boot your usual kernel, but in single-user mode:
```
boot -s
```
To unload your usual kernel and modules, and then load just your old (or another) kernel:
```
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).
Uwaga:
Use the following to load your usual modules with another kernel:
```
unload
set kernel="kernel.old"
boot-conf
```
To load a kernel configuration script (an automated script which does the things you would normally do in the kernel boot-time configurator):
```
load -t userconfig_script /boot/kernel.conf
```

Poprzedni	Początek rozdziału	Następny
12.2. The Booting Problem	Spis treści	12.4. Kernel Interaction During Boot