|Red Hat Enterprise Linux 3: Installation Guide for the x86, Itanium™, and AMD64 Architectures|
|Prev||Appendix A. Upgrading Your Current System||Next|
A software boot loader is used to start Red Hat Enterprise Linux on your computer. It can also start other operating systems, such as Windows. If you are using a Red Hat Enterprise Linux software boot loader (GRUB or LILO), it is detected automatically.
On the Boot Loader Configuration Screen, your options are:
Update boot loader configuration — Choose this option to keep your current boot loader configuration (GRUB or LILO depending on what you have currently installed) and have updates applied.
Skip boot loader updating — Choose this option if you do not want to make any changes to your current boot loader configuration. If you are using a third party boot loader, you should not update your boot loader.
Create new boot loader configuration — Choose this option if you want to create a new boot loader for your system. If you currently have LILO and want to switch to GRUB, or if you have been using boot diskettes to boot your Red Hat Enterprise Linux system and want to use a software boot loader such as GRUB or LILO, create a new boot loader configuration (refer to Section A.3.1 Creating a New Boot Loader Configuration for more information).
Once you have made your selection, click Next to continue.
In order to boot the system without a boot diskette, you usually need to install a boot loader. A boot loader is the first software program that runs when a computer starts. It is responsible for loading and transferring control to the operating system kernel software. The kernel, in turn, initializes the rest of the operating system.
The installation program provides two boot loaders for you to choose from, GRUB and LILO.
GRUB (GRand Unified Bootloader), which is installed by default, is a very powerful boot loader. GRUB can load a variety of free operating systems, as well as proprietary operating systems with chain-loading (the mechanism for loading unsupported operating systems, such as DOS or Windows, by loading another boot loader).
LILO (LInux LOader) is a versatile boot loader for Linux. It does not depend on a specific file system, can boot Linux kernel images from floppy diskettes and hard disks, and can even boot other operating systems.
If you do not want to install GRUB as your boot loader, click Change boot loader. You can then choose to install LILO or choose not to install a boot loader at all.
If you already have a boot loader that can boot Linux and do not want to overwrite your current boot loader, choose Do not install a boot loader by clicking on the Change boot loader button.
If you choose not to install GRUB or LILO for any reason, you will not be able to boot the system directly, and you must use another boot method (such as a boot diskette). Use this option only if you are sure you have another way of booting the system!
Every bootable partition is listed, including partitions used by other operating systems. The partition holding your the system's root file system has a Label of Red Hat Enterprise Linux (for GRUB) or linux (for LILO). Other partitions may also have boot labels. If you would like to add or change the boot label for other partitions that have been detected by the installation program, click once on the partition to select it. Once selected, you can change the boot label by clicking the Edit button.
Select Default beside the preferred boot partition to choose your default bootable OS. You will not be able to move forward in the installation unless you choose a default boot image.
The Label column lists what you must enter at the boot prompt, in non-graphical boot loaders, in order to boot the desired operating system.
Once you have loaded the GRUB boot screen, use the arrow keys to
choose a boot label or type
At the graphical LILO screen, press
Boot loader passwords provide a security mechanism in an environment where physical access to your server is available.
If you are installing a boot loader, you should create a password to protect your system. Without a boot loader password, users with access to your system can pass options to the kernel which can compromise your system security. With a boot loader password in place, the password must first be entered in order to select any non-standard boot options.
If you choose to use a boot loader password to enhance your system security, be sure to select the checkbox labeled Use a boot loader password.
Once selected, enter a password and confirm it.
To configure more advance boot loader options, such as changing the drive order or passing options to the kernel, be sure Configure advanced boot loader options is selected before clicking Next.
Now that you have chosen which boot loader to install, you can also determine where you want the boot loader to be installed. You may install the boot loader in one of two places:
This is the recommended place to install a boot loader, unless the MBR already starts another operating system loader, such as System Commander. The MBR is a special area on your hard drive that is automatically loaded by your computer's BIOS, and is the earliest point at which the boot loader can take control of the boot process. If you install it in the MBR, when your machine boots, GRUB (or LILO) presents a boot prompt. You can then boot Red Hat Enterprise Linux or any other operating system that you have configured the boot loader to boot.
This is recommended if you are already using another boot loader on your system. In this case, your other boot loader takes control first. You can then configure that boot loader to start GRUB (or LILO), which then boots Red Hat Enterprise Linux.
If you have a RAID card, be aware that some BIOSes do not support booting from the RAID card. In cases such as these, the boot loader should not be installed on the MBR of the RAID array. Rather, the boot loader should be installed on the MBR of the same drive as the /boot partition was created.
If your system will use only Red Hat Enterprise Linux, you should choose the MBR.
Click the Change Drive Order button if you would like to rearrange the drive order or if your BIOS does not return the correct drive order. Changing the drive order may be useful if you have multiple SCSI adapters, or both SCSI and IDE adapters, and you want to boot from the SCSI device.
The Force LBA32 (not normally required) option allows you to exceed the 1024 cylinder limit for the /boot partition. If you have a system which supports the LBA32 extension for booting operating systems above the 1024 cylinder limit, and you want to place your /boot partition above cylinder 1024, you should select this option.
While partitioning your hard drive, keep in mind that the BIOS in some older systems cannot access more than the first 1024 cylinders on a hard drive. If this is the case, leave enough room for the /boot Linux partition on the first 1024 cylinders of your hard drive to boot Linux. The other Linux partitions can be after cylinder 1024.
In parted, 1024 cylinders equals 528MB. For more information, refer to:
If you wish to add default options to the boot command, enter them into the Kernel parameters field. Any options you enter are passed to the Linux kernel every time it boots.
If you need to use rescue mode, there are several options available to you.
Using the CD-ROM to boot, type linux rescue at the boot: prompt.
By booting your system from an installation boot diskette made from the bootdisk.img image. This method requires that the Red Hat Enterprise Linux CD-ROM #1 be inserted as the rescue image or that the rescue image be on the hard drive as an ISO image. Once you have booted using this diskette, type linux rescue at the boot: prompt.
If you are performing anything other than a IDE CD-ROM or hard disk installation and are using a boot diskette, you must have at least one driver diskette that you must make in advance. You are prompted by the installation program to insert the driver diskette at the correct time. For more information, refer to Section 2.5.3 Making an Installation Boot Diskette or Appendix E Driver Media.
If you do not wish to use a boot loader, you have several alternatives:
You can load Linux from MS-DOS. Unfortunately, this requires a copy of the Linux kernel (and an initial RAM disk, if you have a SCSI adapter) to be available on an MS-DOS partition. The only way to accomplish this is to boot your Red Hat Enterprise Linux system using some other method (for example, from a boot diskette) and then copy the kernel to an MS-DOS partition. LOADLIN is available from
and associated mirror sites.
SYSLINUX is an MS-DOS program very similar to LOADLIN. It is also available from
and associated mirror sites.
You can load Linux using commercial boot loaders. For example, System Commander and Partition Magic are able to boot Linux (but still require GRUB or LILO to be installed in your Linux root partition).
Boot loaders such as LOADLIN and System Commander are considered to be third-party boot loaders and are not supported by Red Hat.
This section is specific to SMP motherboards only. SMP, short for Symmetric Multiprocessing, is a computer architecture providing fast performance by making multiple CPUs available to complete individual processes simultaneously (multiprocessing).
If the installation program detects an SMP motherboard on your system, it automaticallys create two boot loader entries (depending on the boot loader you installed), rather than the usual single entry.
Intel® Pentium® 4 systems with hyperthreading have an SMP kernel installed by default.
The two GRUB entries are Red Hat Enterprise Linux (kernel version) and Red Hat Enterprise Linux (kernel version-smp). The Red Hat Enterprise Linux (kernel version-smp) boots by default. However, if you have trouble with the SMP kernel, you can elect to boot the Red Hat Enterprise Linux (kernel version) entry instead. This retains all the functionality as before, but you can only operate with a single processor.
The two LILO entries are linux and linux-up. The linux entry boots by default. However, if you have trouble with the SMP kernel, you can elect to boot the linux-up entry instead. This retains all the functionality as before, but you can only operate with a single processor.