GRUB 1.99官方手册：详解安装与引导操作

需积分: 1 85 浏览量更新于2024-07-23 收藏 518KB PDF 举报

本资源是关于GRUB（The Grand Unified Bootloader，统一引导加载器）的官方文档，版本为1.99~beta0，发布日期为2010年11月16日。该文档由Gordon Matzigkeit、Yoshinori K. Okuji、Colin Watson和Colin D. Bennett共同编写，版权归属Free Software Foundation, Inc.。文档遵循GNU Free Documentation License Version 1.2或其后续版本，允许在自由软件协议下复制、分发和修改。首先，文档详细介绍了GRUB的基本概念。1.1节概述了GRUB作为启动加载器的重要性，它是如何在计算机启动过程中负责引导操作系统的过程。1.2节回顾了GRUB的发展历史，包括各个主要版本的迭代更新。 1.3节指出了新版本与前代的主要区别，这可能涉及功能增强、兼容性改进或者对现有问题的修复。1.4节列出了GRUB的主要特性，包括支持多种操作系统（如GNU/Hurd、GNU/Linux、DOS/Windows等）、配置灵活性以及安全措施等。 2.0章节讨论了GRUB的命名约定，这有助于用户理解和配置加载项、设备映射等。3.0章节是安装指南，分为三个部分：3.1介绍grub-install工具用于在系统上安装GRUB；3.2讲述了如何创建一个带有GRUB的可启动CD-ROM；3.3部分解释了BIOS驱动器与操作系统设备之间的映射关系，这对于正确识别和引导不同的硬盘分区至关重要。 4.0章节深入探讨了引导过程。4.1节指导用户如何直接通过GRUB启动操作系统，无论是单个启动还是链式加载。针对特定操作系统，4.2节列出了注意事项，例如GNU/Hurd的特定设置、GNU/Linux的分区管理以及与DOS/Windows交互的问题。这份文档是系统管理员、开发者和高级用户的宝贵参考资料，提供了GRUB的全面安装、配置和使用指南，确保用户能够有效地管理和优化他们的多操作系统启动环境。通过学习和理解这个文档，用户可以充分利用GRUB的强大功能，提升系统的启动效率和安全性。

10 GNU GRUB Manual 1.99~beta0

you need to specify the option ‘--root-directory’. The typical usage is that you create a

GRUB boot ﬂoppy with a ﬁlesystem. Here is an example:

# mke2fs /dev/fd0

# mount -t ext2 /dev/fd0 /mnt

# grub-install --root-directory=/mnt fd0

# umount /mnt

Another example is when you have a separate boot partition which is mounted at

‘/boot’. Since GRUB is a boot loader, it doesn’t know anything about mountpoints at all.

Thus, you need to run grub-install like this:

# grub-install --root-directory=/boot /dev/hda

By the way, as noted above, it is quite diﬃcult to guess BIOS drives correctly under

a UNIX-like OS. Thus, grub-install will prompt you to check if it could really guess the

correct mappings, after the installation. The format is deﬁned in Section 3.3 [Device map],

page 11. Please be quite careful. If the output is wrong, it is unlikely that your computer

will be able to boot with no problem.

Some BIOSes have a bug of exposing the ﬁrst partition of a USB drive as a ﬂoppy

instead of exposing the USB drive as a hard disk (they call it “USB-FDD” boot). In such

cases, you need to install like this:

# losetup /dev/loop0 /dev/sdb1

# mount /dev/loop0 /mnt/usb

# grub-install --boot-directory=/mnt/usb/bugbios --force --allow-floppy /dev/loop0

This install doesn’t conﬂict with standard install as long as they are in separate

directories.

Note that grub-install is actually just a shell script and the real task is done by

grub-mkimage and grub-setup. Therefore, you may run those commands directly to install

GRUB, without using grub-install. Don’t do that, however, unless you are very familiar

with the internals of GRUB. Installing a boot loader on a running OS may be extremely

dangerous.

3.2 Making a GRUB bootable CD-ROM

GRUB supports the no emulation mode in the El Torito speciﬁcation

. This means that

you can use the whole CD-ROM from GRUB and you don’t have to make a ﬂoppy or hard

disk image ﬁle, which can cause compatibility problems.

For booting from a CD-ROM, GRUB uses a special Stage 2 called

‘stage2_eltorito’. The only GRUB ﬁles you need to have in your bootable CD-ROM

are this ‘stage2_eltorito’ and optionally a conﬁg ﬁle ‘grub.cfg’. You don’t need to use

‘stage1’ or ‘stage2’, because El Torito is quite diﬀerent from the standard boot process.

Here is an example of procedures to make a bootable CD-ROM image. First, make

a top directory for the bootable image, say, ‘iso’:

$ mkdir iso

Make a directory for GRUB:

El Torito is a speciﬁcation for bootable CD using BIOS functions.

Chapter 3: Installation 11

$ mkdir -p iso/boot/grub

Copy the ﬁle ‘stage2_eltorito’:

$ cp /usr/lib/grub/i386-pc/stage2_eltorito iso/boot/grub

If desired, make the conﬁg ﬁle ‘grub.cfg’ under ‘iso/boot/grub’ (see Chapter 5

[Conﬁguration], page 17), and copy any ﬁles and directories for the disc to the directory

‘iso/’.

Finally, make a ISO9660 image ﬁle like this:

$ mkisofs -R -b boot/grub/stage2_eltorito -no-emul-boot \

-boot-load-size 4 -boot-info-table -o grub.iso iso

This produces a ﬁle named ‘grub.iso’, which then can be burned into a CD (or a

DVD). mkisofs has already set up the disc to boot from the boot/grub/stage2_eltorito

ﬁle, so there is no need to setup GRUB on the disc. (Note that the -boot-load-size 4 bit

is required for compatibility with the BIOS on many older machines.)

You can use the device ‘(cd)’ to access a CD-ROM in your conﬁg ﬁle. This is not

required; GRUB automatically sets the root device to ‘(cd)’ when booted from a CD-ROM.

It is only necessary to refer to ‘(cd)’ if you want to access other drives as well.

3.3 The map between BIOS drives and OS devices

The grub-mkdevicemap program can be used to create the device map ﬁle. It is often run

automatically by tools such as grub-install if the device map ﬁle does not already exist.

The ﬁle name ‘/boot/grub/device.map’ is preferred.

If the device map ﬁle exists, the GRUB utilities (grub-probe, grub-setup, etc.)

read it to map BIOS drives to OS devices. This ﬁle consists of lines like this:

device file

device is a drive speciﬁed in the GRUB syntax (see Section 11.1 [Device syntax],

page 43), and ﬁle is an OS ﬁle, which is normally a device ﬁle.

Historically, the device map ﬁle was used because GRUB device names had to be

used in the conﬁguration ﬁle, and they were derived from BIOS drive numbers. The map

between BIOS drives and OS devices cannot always be guessed correctly: for example,

GRUB will get the order wrong if you exchange the boot sequence between IDE and SCSI

in your BIOS.

Unfortunately, even OS device names are not always stable. Modern versions of

the Linux kernel may probe drives in a diﬀerent order from boot to boot, and the preﬁx

(‘/dev/hd*’ versus ‘/dev/sd*’) may change depending on the driver subsystem in use. As

a result, the device map ﬁle required frequent editing on some systems.

GRUB avoids this problem nowadays by using UUIDs or ﬁle system labels when

generating ‘grub.cfg’, and we advise that you do the same for any custom menu entries

you write. If the device map ﬁle does not exist, then the GRUB utilities will assume a

temporary device map on the ﬂy. This is often good enough, particularly in the common

case of single-disk systems.

However, the device map ﬁle is not entirely obsolete yet, and there are still some

situations that require it to exist. If necessary, you may edit the ﬁle if grub-mkdevicemap

makes a mistake. You can put any comments in the ﬁle if needed, as the GRUB utilities

assume that a line is just a comment if the ﬁrst character is ‘#’.

Chapter 4: Booting 13

4 Booting

GRUB can load Multiboot-compliant kernels in a consistent way, but for some free operating

systems you need to use some OS-speciﬁc magic.

4.1 How to boot operating systems

GRUB has two distinct boot methods. One of the two is to load an operating system directly,

and the other is to chain-load another boot loader which then will load an operating system

actually. Generally speaking, the former is more desirable, because you don’t need to install

or maintain other boot loaders and GRUB is ﬂexible enough to load an operating system

from an arbitrary disk/partition. However, the latter is sometimes required, since GRUB

doesn’t support all the existing operating systems natively.

4.1.1 How to boot an OS directly with GRUB

Multiboot (see Section “Motivation” in The Multiboot Speciﬁcation) is the native format

supported by GRUB. For the sake of convenience, there is also support for Linux, FreeBSD,

NetBSD and OpenBSD. If you want to boot other operating systems, you will have to

chain-load them (see Section 4.1.2 [Chain-loading], page 13).

FIXME: this section is incomplete.

1. Run the command boot (see Section 13.3.4 [boot], page 50).

However, DOS and Windows have some deﬁciencies, so you might have to use more

complicated instructions. See Section 4.2.3 [DOS/Windows], page 15, for more information.

4.1.2 Chain-loading an OS

Operating systems that do not support Multiboot and do not have speciﬁc support in

GRUB (speciﬁc support is available for Linux, FreeBSD, NetBSD and OpenBSD) must be

chain-loaded, which involves loading another boot loader and jumping to it in real mode.

The chainloader command (see Section 13.3.6 [chainloader], page 50) is used to set

this up. It is normally also necessary to load some GRUB modules and set the appropriate

root device. Putting this together, we get something like this, for a Windows system on the

ﬁrst partition of the ﬁrst hard disk:

menuentry "Windows" {

insmod chain

insmod ntfs

set root=(hd0,1)

chainloader +1

}

On systems with multiple hard disks, an additional workaround may be required.

See Section 4.2.3 [DOS/Windows], page 15.

Chain-loading is only supported on PC BIOS and EFI platforms.

4.2 Some caveats on OS-speciﬁc issues

Here, we describe some caveats on several operating systems.

14 GNU GRUB Manual 1.99~beta0

4.2.1 GNU/Hurd

Since GNU/Hurd is Multiboot-compliant, it is easy to boot it; there is nothing special about

it. But do not forget that you have to specify a root partition to the kernel.

1. Set GRUB’s root device to the same drive as GNU/Hurd’s. The command search --

file --set /boot/gnumach.gz or similar may help you (see Section 13.3.32 [search],

page 55).

2. Load the kernel and the modules, like this:

grub> multiboot /boot/gnumach.gz root=device:hd0s1

grub> module /hurd/ext2fs.static ext2fs --readonly \

--multiboot-command-line=’${kernel-command-line}’ \

--host-priv-port=’${host-port}’ \

--device-master-port=’${device-port}’ \

--exec-server-task=’${exec-task}’ -T typed ’${root}’ \

’$(task-create)’ ’$(task-resume)’

grub> module /lib/ld.so.1 exec /hurd/exec ’$(exec-task=task-create)’

3. Finally, run the command boot (see Section 13.3.4 [boot], page 50).

4.2.2 GNU/Linux

It is relatively easy to boot GNU/Linux from GRUB, because it somewhat resembles to

boot a Multiboot-compliant OS.

1. Set GRUB’s root device to the same drive as GNU/Linux’s. The command search

--file --set /vmlinuz or similar may help you (see Section 13.3.32 [search], page 55).

2. Load the kernel using the command linux (see Section 13.3.23 [linux], page 53):

grub> linux /vmlinuz root=/dev/sda1

If you need to specify some kernel parameters, just append them to the command. For

example, to set ‘acpi’ to ‘off’, do this:

grub> linux /vmlinuz root=/dev/sda1 acpi=off

See the documentation in the Linux source tree for complete information on the avail-

able options.

With linux GRUB uses 32-bit protocol. Some BIOS services like APM or EDD aren’t

available with this protocol. In this case you need to use linux16

grub> linux16 /vmlinuz root=/dev/sda1 acpi=off

3. If you use an initrd, execute the command initrd (see Section 13.3.19 [initrd], page 53)

after linux:

grub> initrd /initrd

If you used linux16 you need to use initrd16:

grub> initrd16 /initrd

4. Finally, run the command boot (see Section 13.3.4 [boot], page 50).

Caution: If you use an initrd and specify the ‘mem=’ option to the kernel to let it use

less than actual memory size, you will also have to specify the same memory size to GRUB.

To let GRUB know the size, run the command uppermem before loading the kernel. See

Section 13.3.36 [uppermem], page 58, for more information.

剩余97页未读，继续阅读

richeir

粉丝: 0

GRUB 1.99官方手册：详解安装与引导操作

grub2官方文档

Grub4dos 文档

GRUB使用指南.doc

grub2 2.02版本官方文档

grub2教程,pdf文档2篇

GRUB多系统引导、系统引导文档

Grub4dos使用教程

grub4dos最新帮助文档(2011-05-04)CHM格式

Grub installer

grub教程

最新资源