Changeset 908631a

Timestamp:

04/14/2001 10:23:28 PM (23 years ago)

Author:

Gerard Beekmans <gerard@…>

Branches:

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

Children:

9ef3d9c

Parents:

fa50d69

Message:

Don't run lilo inside chroot anymore

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

File:

• chapter08/lilo.xml (modified) (2 diffs)

chapter08/lilo.xml

@@ -1 +1 @@
 <sect1 id="ch08-lilo">
-<title>Adding an entry to LILO</title>
+<title>Making the LFS system bootable</title>
 
 <para>
-In order to being able to boot from this partition, we need to update our
-/etc/lilo.conf file. The following lines get added to lilo.conf by running:
+In order to being able to boot the LFS system, we need to update our
+bootloader. We're assuming that your host system is using Lilo (since
+that's the most commonly used boot loader at the moment).
+</para>
+
+<para>
+We will not be running the lilo program inside chroot. Running lilo
+inside chroot can have fatal side-effects which render your MBR useles
+and you'd need a boot disk to be able to start any Linux system (either
+the host system or the LFS system).
+</para>
+
+<para>
+First we'll exit chroot and copy the lfskernel file to the host system:
+</para>
+
+<blockquote><literallayout>
+
+        <userinput>logout &amp;&amp;</userinput>
+        <userinput>cp $LFS/boot/lfskernel /boot
+                &amp;&amp;</userinput>
+
+</literallayout></blockquote>
+
+<para>
+The next step is adding an entry to /etc/lilo.conf so that we can
+choose LFS when booting the computer:
 </para>
 
 <literallayout>
 
-<userinput>cat &gt;&gt; /etc/lilo.conf &lt;&lt; "EOF"</userinput>
-image=/boot/lfskernel
-        label=lfs
-        root=&lt;partition&gt;
-        read-only
-<userinput>EOF</userinput>
+        <userinput>cat &gt;&gt; /etc/lilo.conf &lt;&lt; "EOF"</userinput>
+                image=/boot/lfskernel
+                label=lfs
+                root=&lt;partition&gt;
+                read-only
+        <userinput>EOF</userinput>
 
 </literallayout>
 
 <para>
-&lt;partition&gt; must be replaced by the partition's designation (which
-would be /dev/hda5 in my case).
+&lt;partition&gt; must be replaced by the LFS partition's designation.
 </para>
 
@@ -33 +57 @@
 </literallayout></blockquote>
 
+<para>
+The last step is syncing the host system lilo config. files with the
+LFS system:
+</para>
+
+<blockquote><literallayout>
+
+        <userinput>cp /etc/lilo.conf $LFS/etc &amp;&amp;</userinput>
+        <userinput>cp &lt;kernel images&gt; $LFS/boot</userinput>
+
+</literallayout></blockquote>
+
+<para>
+To find out which kernel images files are being used, look at the
+/etc/lilo.conf file and find the lines starting with
+<emphasis>image=</emphasis>. If your host system has kernel files in
+other places than the /boot directory, make sure you update the paths
+in the $LFS/etc/lilo.conf file so that it does look for them in the
+/boot directory.
+</para>
+
 </sect1>