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:
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 DragonFly 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 DragonFly, 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=DragonFly
In the above, specify DragonFly'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.
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 disklabel (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.
They are found on the boot sector of the boot slice, which is where boot0, or any other program on the MBR expects to find the program to run to continue the boot process. The files in the /boot directory are copies of the real files, which are stored outside of the DragonFly file system.
boot1 is very simple, since it can only be 512 bytes in size, and knows just enough about the DragonFly disklabel, which stores information about the slice, to find and execute boot2.
boot2 is slightly more sophisticated, and understands the DragonFly 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.
If you ever need to replace the installed boot1 and boot2 use disklabel(8):
# disklabel -B diskslice
where diskslice is the disk and slice you boot from, such as ad0s1 for the first slice on the first IDE disk.
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.
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.
These are the most commonly used loader commands. For a complete discussion of all available commands, please see loader(8).
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.
Immediately proceeds to boot the kernel, with the given options, if any, and with the kernel name given, if it is.
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.
Shows help messages read from /boot/loader.help. If the topic given is index, then the list of available topics is given.
Processes the file with the given filename. The file is read in, and interpreted line by line. An error immediately stops the include command.
Loads the kernel, kernel module, or file of the type given, with the filename given. Any arguments after filename are passed to the file.
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
Lists all of the devices from which it may be
possible to load modules. If
specified, more details are printed.
Displays loaded modules. If
specified, more details are shown.
Displays the files specified, with a pause at each
Immediately reboots the system.
Sets the loader's environment variables.
Removes all loaded modules.
Here are some practical examples of loader usage:
To simply boot your usual kernel, but in single-user mode:
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).
Note: 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
Contact the Documentation mailing list for comments, suggestions and questions about this document.