source: chapter08/lilo.xml@ a3f60e1e

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 11.2 11.2-rc1 11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 6.0 6.1 6.1.1 6.3 6.4 6.5 6.6 6.7 6.8 7.0 7.1 7.2 7.3 7.4 7.5 7.5-systemd 7.6 7.6-systemd 7.7 7.7-systemd 7.8 7.8-systemd 7.9 7.9-systemd 8.0 8.1 8.2 8.3 8.4 9.0 9.1 arm bdubbs/gcc13 ml-11.0 multilib renodr/libudev-from-systemd s6-init trunk v3_0 v3_1 v3_2 v3_3 v4_0 v4_1 v5_0 v5_1 v5_1_1 xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/lfs-next xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since a3f60e1e was 8ef599c, checked in by Simon Perreault <nomis80@…>, 23 years ago

Removed blank lines after <literallayout> and before </literallayout>

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@520 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 2.1 KB
Line 
1<sect1 id="ch08-lilo">
2<title>Making the LFS system bootable</title>
3
4<para>
5In order to being able to boot the LFS system, we need to update our
6bootloader. We're assuming that your host system is using Lilo (since
7that's the most commonly used boot loader at the moment).
8</para>
9
10<para>
11We will not be running the lilo program inside chroot. Running lilo
12inside chroot can have fatal side-effects which render your MBR useles
13and you'd need a boot disk to be able to start any Linux system (either
14the host system or the LFS system).
15</para>
16
17<para>
18First we'll exit chroot and copy the lfskernel file to the host system:
19</para>
20
21<blockquote><literallayout>
22 <userinput>logout</userinput>
23 <userinput>cp $LFS/boot/lfskernel /boot</userinput>
24</literallayout></blockquote>
25
26<para>
27The next step is adding an entry to /etc/lilo.conf so that we can
28choose LFS when booting the computer:
29</para>
30
31<literallayout>
32 <userinput>cat &gt;&gt; /etc/lilo.conf &lt;&lt; "EOF"</userinput>
33 image=/boot/lfskernel
34 label=lfs
35 root=&lt;partition&gt;
36 read-only
37 <userinput>EOF</userinput>
38</literallayout>
39
40<para>
41&lt;partition&gt; must be replaced by the LFS partition's designation.
42</para>
43
44<para>
45Now the boot loader gets updated by running:
46</para>
47
48<blockquote><literallayout>
49 <userinput>/sbin/lilo</userinput>
50</literallayout></blockquote>
51
52<para>
53The last step is syncing the host system lilo config. files with the
54LFS system:
55</para>
56
57<blockquote><literallayout>
58 <userinput>cp /etc/lilo.conf $LFS/etc &amp;&amp;</userinput>
59 <userinput>cp &lt;kernel images&gt; $LFS/boot</userinput>
60</literallayout></blockquote>
61
62<para>
63To find out which kernel images files are being used, look at the
64/etc/lilo.conf file and find the lines starting with
65<emphasis>image=</emphasis>. If your host system has kernel files in
66other places than the /boot directory, make sure you update the paths
67in the $LFS/etc/lilo.conf file so that it does look for them in the
68/boot directory.
69</para>
70
71<para>
72As soon as we have booted into LFS we can run
73<userinput>/sbin/lilo</userinput> from the LFS system in order to have
74the latest Lilo version in the MBR.
75</para>
76
77</sect1>
78
Note: See TracBrowser for help on using the repository browser.