source: BOOK/boot/x86_64-64/bootloaders.xml@ 600339f5

clfs-1.2 clfs-2.1 clfs-3.0.0-systemd clfs-3.0.0-sysvinit systemd sysvinit
Last change on this file since 600339f5 was 48b28ab, checked in by Jim Gifford <clfs@…>, 19 years ago

r2552@server (orig r1265): ken | 2006-03-12 15:28:07 -0800
Use Lilo for x86_64-64

  • Property mode set to 100644
File size: 1.4 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
3 "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
6]>
7
8<sect1 id="ch-boot-building-a-bootloader" role="wrap">
9 <?dbhtml filename="building-a-bootloader.html"?>
10
11 <title>Building a bootloader</title>
12
13 <para>On x86 and x86_64 (multilib) architectures, the preferred
14 bootloader is Grub. Unfortunately, Grub doesn&quot;t work on x86_64
15 Pure64 - the stage2 files can be correctly built as 32-bit, but the
16 grub shell is a 64-bit program, and tries to execute some of the
17 stage2 routines - this results in a segmentation fault. Therefore,
18 in the final system we use Lilo as the bootloader.
19 </para>
20
21 <para>If you already have a bootloader, such as Grub, installed on
22 the system then you should use that to make your new kernel bootable.
23 </para>
24
25 <note>
26 <para>We will now cross-compile Bin86 and Lilo - these instructions
27 assume you are using an x86_64 machine (e.g. booted fron a Live CD),
28 either pure64 or multilib. This approach will not work if you are
29 running the machine as i686, because a 32-bit kernel will not be
30 able to execute a 64-bit binary to install the bootloader. If that
31 is the case, you will need to install an i686 bootloader on the
32 host system.
33 </para>
34 </note>
35
36</sect1>
Note: See TracBrowser for help on using the repository browser.