GNU GRUB 0.97 官方手册：深入学习引导装载程序

需积分: 11 102 浏览量更新于2024-07-24 1 收藏 503KB PDF 举报

"GNU GRUB 0.97 官方文档提供了详细的引导装载程序 GNU GRUB 的相关信息，包括版本 0.97 (2005年5月8日) 的详细介绍。文档由 Gordon Matzigkeit 和 Yoshinori K. Okuji 编写，并受 GNU Free Documentation License 保护，允许复制、分发和修改。该文档包含从基本概念到安装步骤的全面指南。" GNU GRUB 是一个强大的引导装载程序（bootloader），它的全称是 Grand Unified Bootloader。其主要功能是帮助计算机在启动时选择并加载操作系统。这个文档涵盖了以下几个关键知识点： 1. **简介**： - **概述**：介绍 GRUB 的基本概念，它是一个多启动管理器，支持启动多种操作系统，如 Linux、Windows 等。 - **历史**：简述 GRUB 的发展历程，它始于1999年，逐渐发展成为广泛使用的引导装载程序。 - **特性**：列举了 GRUB 的一些关键功能，如支持多平台、可配置性高、支持动态加载内核模块等。 - **引导装载程序的角色**：解释了引导装载程序在系统启动过程中的作用，负责加载内核并传递启动参数。 2. **命名约定**： - 这一部分可能讲解了 GRUB 中用于标识设备和文件系统的命名规则，例如 `/dev/hda` 或 `/dev/sda` 表示硬盘，`/boot/grub/menu.lst` 是 GRUB 的配置文件等。 3. **安装**： - **创建 GRUB 引导软盘**：说明如何制作一个包含 GRUB 的启动盘，以便在没有预装 GRUB 的系统上进行安装。 - **原生安装 GRUB**：描述如何直接将 GRUB 安装到系统硬盘的主引导记录（MBR）或分区引导扇区。 - **使用 grub-install 安装 GRUB**：介绍使用 `grub-install` 命令行工具进行自动化安装的过程。 - **创建 GRUB 启动菜单**：可能包括了如何配置 GRUB 启动菜单，添加、删除或修改启动项的详细步骤。文档的其余部分可能会涵盖更多高级主题，如配置文件的详细解析、GRUB 命令行使用、处理启动问题以及调试技巧等。对于想要深入理解 GRUB 或者需要解决与引导相关问题的用户，这份官方文档是一份宝贵的参考资料。由于原始内容未提供完整章节，具体的细节无法在此详述，但可以肯定的是，通过阅读这份文档，读者将能够全面了解和掌握 GRUB 0.97 的各项功能和操作方法。

10 GNU GRUB Manual 0.97

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:

$ 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 ‘menu.lst’ 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.

Chapter 4: Booting 11

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

Generally, GRUB can boot any Multiboot-compliant OS in the following steps:

1. Set GRUB’s root device to the drive where the OS images are stored with the command

root (see Section 13.3.31 [root], page 47).

2. Load the kernel image with the command kernel (see Section 13.3.20 [kernel], page 46).

3. If you need modules, load them with the command module (see Section 13.3.25 [mod-

ule], page 47) or modulenounzip (see Section 13.3.26 [modulenounzip], page 47).

4. Run the command boot (see Section 13.3.2 [boot], page 42).

Linux, FreeBSD, NetBSD and OpenBSD can be booted in a similar manner. You

load a kernel image with the command kernel and then run the command boot. If the

kernel requires some parameters, just append the parameters to kernel, after the ﬁle name

of the kernel. Also, please refer to Section 4.2 [OS-speciﬁc notes], page 12, for information

on your OS-speciﬁc issues.

4.1.2 Load another boot loader to boot unsupported operating

systems

If you want to boot an unsupported operating system (e.g. Windows 95), chain-load a boot

loader for the operating system. Normally, the boot loader is embedded in the boot sector

of the partition on which the operating system is installed.

1. Set GRUB’s root device to the partition by the command rootnoverify (see Sec-

tion 13.3.32 [rootnoverify], page 48):

grub> rootnoverify (hd0,0)

2. Set the active ﬂag in the partition using the command makeactive

(see Section 13.3.22

[makeactive], page 46):

grub> makeactive

This is not necessary for most of the modern operating systems.

12 GNU GRUB Manual 0.97

3. Load the boot loader with the command chainloader (see Section 13.3.4 [chainloader],

page 42):

grub> chainloader +1

‘+1’ indicates that GRUB should read one sector from the start of the partition. The

complete description about this syntax can be found in Section 11.3 [Block list syntax],

page 32.

4. Run the command boot (see Section 13.3.2 [boot], page 42).

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

complicated instructions. See

Section 4.2.6 [DOS/Windows], page 13, for more information.

4.2 Some caveats on OS-speciﬁc issues

Here, we describe some caveats on several operating systems.

4.2.1 GNU/Hurd

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

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

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

find /boot/gnumach or similar can help you (see Section 13.3.11 [ﬁnd], page 43).

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

grub> kernel /boot/gnumach root=hd0s1

grub> module /boot/serverboot

3. Run the command boot (see Section 13.3.2 [boot], page 42).

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. Probably the command

find /vmlinuz or similar can help you (see Section 13.3.11 [ﬁnd], page 43).

2. Load the kernel:

grub> kernel /vmlinuz root=/dev/hda1

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

example, to set ‘vga’ to ‘ext’, do this:

grub> kernel /vmlinuz root=/dev/hda1 vga=ext

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

able options.

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

after kernel:

grub> initrd /initrd

4. Finally, run the command boot (see

Section 13.3.2 [boot], page 42).

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.37 [uppermem], page 49, for more information.

Chapter 4: Booting 13

4.2.3 FreeBSD

GRUB can load the kernel directly, either in ELF or a.out format. But this is not recom-

mended, since FreeBSD’s bootstrap interface sometimes changes heavily, so GRUB can’t

guarantee to pass kernel parameters correctly.

Thus, we’d recommend loading the very ﬂexible loader ‘/boot/loader’ instead. See

this example:

grub> root (hd0,a)

grub> kernel /boot/loader

grub> boot

4.2.4 NetBSD

GRUB can load NetBSD a.out and ELF directly, follow these steps:

1. Set GRUB’s root device with root (see Section 13.3.31 [root], page 47).

2. Load the kernel with kernel (se e Section 13.3.20 [kernel], page 46). You should append

the ugly option ‘--type=netbsd’, if you want to load an ELF kernel, like this:

grub> kernel --type=netbsd /netbsd-elf

3. Run boot (see Section 13.3.2 [boot], page 42).

For now, however, GRUB do es n’t allow you to pass kernel parameters, so it may

be better to chain-load it instead. For more information, please see Section 4.1.2 [Chain-

loading], page 11

4.2.5 OpenBSD

The booting instruction is exactly the same as for NetBSD (see Section 4.2.4 [NetB SD],

page 13).

4.2.6 DOS/Windows

GRUB cannot boot DOS or Windows directly, so you must chain-load them (see Sec-

tion 4.1.2 [Chain-loading], page 11). However, their boot loaders have some critical deﬁ-

ciencies, so it may not work to just chain-load them. To overcome the problems, GRUB

provides you with two helper functions.

If you have installed DOS (or Windows) on a non-ﬁrst hard disk, you have to use

the disk swapping technique, because that OS cannot boot from any disks but the ﬁrst one.

The workaround used in GRUB is the command map (see Section 13.3.23 [map], page 46),

like this:

grub> map (hd0) (hd1)

grub> map (hd1) (hd0)

This performs a virtual swap be tween your ﬁrst and second hard drive.

Caution: This is eﬀective only if DOS (or Windows) uses BIOS to access the swapped

disks. If that OS uses a special driver for the disks, this probably won’t work.

Another problem arises if you installed more than one set of DOS/Windows onto

one disk, because they could be confused if there are more than one primary partitions for

DOS/Windows. Certainly you should avoid doing this, but there is a solution if you do

want to do so. Use the partition hiding/unhiding technique.

14 GNU GRUB Manual 0.97

If GRUB hides a DOS (or Windows) partition (see Section 13.2.5 [hide], page 37),

DOS (or Windows) will ignore the partition. If GRUB unhides a DOS (or Windows) par-

tition (see Section 13.2.17 [unhide], page 42), DOS (or Windows) will detect the partition.

Thus, if you have installed DOS (or Windows) on the ﬁrst and the second partition of the

ﬁrst hard disk, and you want to boot the copy on the ﬁrst partition, do the following:

grub> unhide (hd0,0)

grub> hide (hd0,1)

grub> rootnoverify (hd0,0)

grub> chainloader +1

grub> makeactive

grub> boot

4.2.7 SCO UnixWare

It is known that the signature in the boot loader for SCO UnixWare is wrong, so you

will have to spec ify the option ‘--force’ to chainloader (see

Section 13.3.4 [chainloader],

page 42), like this:

grub> rootnoverify (hd1,0)

grub> chainloader --force +1

grub> makeactive

grub> boot

4.2.8 QNX

QNX seems to use a bigger boot loader, so you need to boot it up, like this:

grub> rootnoverify (hd1,1)

grub> chainloader +4

grub> boot

4.3 How to make your system robust

When you test a new kernel or a new OS, it is important to make sure that your computer

can boot even if the new system is unbootable. This is crucial especially if you maintain

servers or remote systems. To accomplish this goal, you need to set up two things:

1. You must maintain a sys tem which is always bootable. For instance, if you test a new

kernel, you need to kee p a working kernel in a diﬀerent place. And, it would sometimes

be very nice to even have a complete copy of a working system in a diﬀerent partition

or disk.

2. You must direct GRUB to boot a working system when the new system fails. This is

possible with the fallback system in GRUB.

The former requirement is very speciﬁc to each OS, so this documentation does not

cover that topic. It is bette r to consult some backup tools.

So let’s see the GRUB part. There are two possibilities: one of them is quite simple

but not very robust, and the other is a bit complex to set up but probably the best solution

to make sure that your system can start as long as GRUB itself is bootable.

剩余95页未读，继续阅读

dc2013

粉丝: 4
资源: 5

GNU GRUB 0.97 官方手册：深入学习引导装载程序

linux开机grub终极解决方法

GNU GRUB 4(version0.4.4)

GNU GRUB Manual 0.97.html

gnu grub version 0.97

GRUB 0.97手册：详解GNU统一引导加载器的安装与管理

gnu grub 097

GNU GRUB 官方用户手册

gnu grub version 2.06

GNU GRUB version 2.02

gnu grub version 2.04

最新资源