1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
|
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % general-entities SYSTEM "../general.ent">
%general-entities;
]>
<sect1 id="ch-bootable-grub" role="wrap">
<?dbhtml filename="grub.html"?>
<sect1info condition="script">
<productname>grub</productname>
<productnumber>&grub-version;</productnumber>
<address>&grub-url;</address>
</sect1info>
<title>Using GRUB to Set Up the Boot Process</title>
<note>
<para>
If your system has UEFI support and you wish to boot LFS with UEFI,
you should skip this page, and config GRUB with UEFI support
using the instructions provided in
<ulink url="&blfs-book;postlfs/grub-setup.html">the BLFS page</ulink>.
</para>
</note>
<sect2>
<title>Introduction</title>
<warning><para>Configuring GRUB incorrectly can render your system
inoperable without an alternate boot device such as a CD-ROM or bootable
USB drive. This section is not required to boot your LFS system. You may
just want to modify your current boot loader, e.g. Grub-Legacy, GRUB2, or
LILO.</para></warning>
<para> Ensure that an emergency boot disk is ready to <quote>rescue</quote>
the computer if the computer becomes unusable (un-bootable). If you do not
already have a boot device, you can create one. In order for the procedure
below to work, you need to jump ahead to BLFS and install
<userinput>xorriso</userinput> from the <ulink
url="&blfs-book;multimedia/libisoburn.html">
libisoburn</ulink> package.</para>
<screen role="nodump"><userinput>cd /tmp
grub-mkrescue --output=grub-img.iso
xorriso -as cdrecord -v dev=/dev/cdrw blank=as_needed grub-img.iso</userinput></screen>
</sect2>
<sect2>
<title>GRUB Naming Conventions</title>
<para>GRUB uses its own naming structure for drives and partitions in
the form of <emphasis>(hdn,m)</emphasis>, where <emphasis>n</emphasis>
is the hard drive number and <emphasis>m</emphasis> is the partition
number. The hard drive number starts from zero, but the partition number
starts from one for normal partitions and five for extended partitions.
Note that this is different from earlier versions where
both numbers started from zero. For example, partition <filename
class="partition">sda1</filename> is <emphasis>(hd0,1)</emphasis> to
GRUB and <filename class="partition">sdb3</filename> is
<emphasis>(hd1,3)</emphasis>. In contrast to Linux, GRUB does not
consider CD-ROM drives to be hard drives. For example, if using a CD
on <filename class="partition">hdb</filename> and a second hard drive
on <filename class="partition">hdc</filename>, that second hard drive
would still be <emphasis>(hd1)</emphasis>.</para>
</sect2>
<sect2>
<title>Setting Up the Configuration</title>
<para>GRUB works by writing data to the first physical track of the
hard disk. This area is not part of any file system. The programs
there access GRUB modules in the boot partition. The default location
is /boot/grub/.</para>
<para>The location of the boot partition is a choice of the user that
affects the configuration. One recommendation is to have a separate small
(suggested size is 200 MB) partition just for boot information. That way
each build, whether LFS or some commercial distro, can access the same boot
files and access can be made from any booted system. If you choose to do
this, you will need to mount the separate partition, move all files in the
current <filename class="directory">/boot</filename> directory (e.g. the
linux kernel you just built in the previous section) to the new partition.
You will then need to unmount the partition and remount it as <filename
class="directory">/boot</filename>. If you do this, be sure to update
<filename>/etc/fstab</filename>.</para>
<para>Using the current lfs partition will also work, but configuration
for multiple systems is more difficult.</para>
<para>Using the above information, determine the appropriate
designator for the root partition (or boot partition, if a separate
one is used). For the following example, it is assumed that the root
(or separate boot) partition is <filename
class="partition">sda2</filename>.</para>
<para>Install the GRUB files into <filename
class="directory">/boot/grub</filename> and set up the boot track:</para>
<warning>
<para>The following command will overwrite the current boot loader. Do not
run the command if this is not desired, for example, if using a third party
boot manager to manage the Master Boot Record (MBR).</para>
</warning>
<screen role="nodump"><userinput>grub-install /dev/sda</userinput></screen>
<note>
<para>If the system has been booted using UEFI,
<command>grub-install</command> will try to install files for the
<emphasis>x86_64-efi</emphasis> target, but those files
have not been installed in <xref linkend="chapter-building-system"/>.
If this is the case, add <option>--target i386-pc</option> to the
command above.</para>
</note>
<!-- This does not seem to be true any more
<note><para><application>grub-install</application> is a script and calls another
program, grub-probe, that may fail with a message "cannot stat `/dev/root'".
If so, create a temporary symbolic link from your root partition to /dev/root:</para>
<screen role="nodump"><userinput>ln -sv /dev/sda2 /dev/root</userinput></screen>
<para>The symbolic link will only be present until the system is rebooted.
The link is only needed for the installation procedure.
</para></note>
-->
</sect2>
<sect2 id="grub-cfg">
<title>Creating the GRUB Configuration File</title>
<para>Generate <filename>/boot/grub/grub.cfg</filename>:</para>
<screen revision="sysv"><userinput>cat > /boot/grub/grub.cfg << "EOF"
<literal># Begin /boot/grub/grub.cfg
set default=0
set timeout=5
insmod ext2
set root=(hd0,2)
menuentry "GNU/Linux, Linux &linux-version;-lfs-&version;" {
linux /boot/vmlinuz-&linux-version;-lfs-&version; root=/dev/sda2 ro
}</literal>
EOF</userinput></screen>
<screen revision="systemd"><userinput>cat > /boot/grub/grub.cfg << "EOF"
<literal># Begin /boot/grub/grub.cfg
set default=0
set timeout=5
insmod ext2
set root=(hd0,2)
menuentry "GNU/Linux, Linux &linux-version;-lfs-&versiond;" {
linux /boot/vmlinuz-&linux-version;-lfs-&versiond; root=/dev/sda2 ro
}</literal>
EOF</userinput></screen>
<note><para>From <application>GRUB</application>'s perspective, the
kernel files are relative to the partition used. If you
used a separate /boot partition, remove /boot from the above
<emphasis>linux</emphasis> line. You will also need to change the
<emphasis>set root</emphasis> line to point to the boot partition.
</para></note>
<para>GRUB is an extremely powerful program and it provides a tremendous
number of options for booting from a wide variety of devices, operating
systems, and partition types. There are also many options for customization
such as graphical splash screens, playing sounds, mouse input, etc. The
details of these options are beyond the scope of this introduction.</para>
<caution><para>There is a command, <application>grub-mkconfig</application>, that
can write a configuration file automatically. It uses a set of scripts in
/etc/grub.d/ and will destroy any customizations that you make. These scripts
are designed primarily for non-source distributions and are not recommended for
LFS. If you install a commercial Linux distribution, there is a good chance
that this program will be run. Be sure to back up your grub.cfg file.</para></caution>
</sect2>
</sect1>
|
