source: BOOK/boot/x86_64-64/lilo.xml @ fb40919

clfs-1.2clfs-2.1clfs-3.0.0-systemdclfs-3.0.0-sysvinitsystemdsysvinit
Last change on this file since fb40919 was fb40919, checked in by Chris Staub <chris@…>, 13 years ago

Changed many 'LFS' references to 'CLFS'

  • Property mode set to 100644
File size: 4.6 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-lilo">
9  <?dbhtml filename="lilo.html"?>
10
11  <title>Making the CLFS System Bootable</title>
12
13  <indexterm zone="ch-boot-lilo">
14    <primary sortas="a-Lilo">Lilo</primary>
15    <secondary>configuring</secondary>
16  </indexterm>
17
18  <para os="a">You are nearly ready to boot to the new temporary system.
19  One of the last things to do is to ensure that the system can be booted.
20  The instructions below apply only to x86_64 machines on which lilo is going
21  to be installed. Information on using a pre-installed Grub on machines
22  currently running as x86 or x86_64 multilib should be available in the
23  usual resource-specific locations for those architectures.  If you have
24  installed an x86 version of lilo, these instructions should be modified
25  to refer to the <command>lilo</command> and <command>keytab-lilo.pl
26  </command> commands you installed on the host system.</para>
27
28  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
29  href="../x86/grub.xml"
30  xpointer="xpointer(//*[@os='b'])"/>
31
32  <para os="c">If you have multiple systems on your machine using a different
33  bootloader such as grub, you may prefer to use that instead - consult the
34  appropriate documentation.  The rest of this section assumes you are going
35  to use lilo.</para> 
36
37  <para os="d">Earlier, we compiled and installed the Lilo boot loader software
38  in preparation for this step. The procedure involves writing a boot image to
39  a specific location on the hard drive. If you have a floppy disk drive, or
40  if you have installed a cd recording program, we highly recommend using
41  mkrescue to create a Lilo boot floppy, or CD (using e.g. dvdrecord from
42  dvdrtools) as a test and as a backup.</para>
43
44  <para os="e">Normally, you interact with lilo by using the cursor and enter
45  keys to select from the available option(s), but sometimes it is necessary to
46  add other boot options, such as e.g. 'init=/bin/bash' to debug boot failures.
47  The more your keyboard layout differs from the US qwerty layout, the harder
48  it will be to type boot options unless lilo knows about your keyboard layout.
49  So, we will create a key table for Lilo (.ktl) file - at one point in the
50  documentation these are referred to as .klt files, which may be a typo, but
51  has been followed by some distros.  The name, and location, are not important
52  but it is conventional to put these in /boot with the name representing the
53  key layout.  For a British keyboard layout, the following command will
54  achieve this:</para> 
55
56<screen os="f" role="nodump"><userinput>keytab-lilo.pl uk >i${LFS}/boot/uk.ktl</userinput></screen>
57
58  <para os="g">The argument to the command is the name of the keymap, or if
59    necessary you can specify the full path to the keymap.  Use whatever
60    is appropriate for your keyboard.</para>
61
62  <para os="i">The next step is to create /etc/lilo.conf</para>
63
64<screen os="j" role="nodump"><userinput>cat &gt; ${LFS}/etc/lilo.conf &lt;&lt; "EOF"
65<literal># Begin /etc/lilo.conf
66# lilo.conf
67#
68# global options
69boot=/dev/&lt;bootdisk&gt;
70keytable=/boot/&lt;keytable&gt;
71lba32
72map=/boot/map
73prompt
74
75# set the name of the default image to boot
76default=lfs
77
78# define an image
79image=/boot/lfskernel
80    label=lfs
81    root=/dev/&lt;partition&gt;
82    read-only
83# optionally add parameters to pass, e.g.
84#   append="video=radeonfb:1024x768-16@70"
85
86# if you had an existing system, you could
87# add its details here.
88EOF</literal></userinput></screen>
89
90
91  <para os="k">Replace &lt;bootdisk&gt; with the name of the disk (or
92    partition) on which the boot sector is to be written, e.g. sda. Replace
93    &lt;keytable&gt; with the name of the keytable file you created, and
94    &lt;partition&gt; with the name of the root partition for the new
95    system.
96  </para>
97
98  <warning os="l">
99    <para>The following command will overwrite any current boot loader.
100    Do not run the command if this is not desired. If you have
101    cross-compiled on a different machine from the target, you must
102    install the bootloader on the target machine, the installed boot
103    block is not a file which can be copied with <command>tar</command>.
104    </para>
105  </warning>
106
107  <para os="m">Run Lilo:</para>
108
109<screen os="n" role="nodump"><userinput>/tools/bin/lilo-static -v</userinput></screen>
110
111  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
112  href="../../bootable/x86_64-64/lilo.xml"
113  xpointer="xpointer(//*[@os='o'])"/>
114
115</sect1>
Note: See TracBrowser for help on using the repository browser.