source: chapter08/lilo.xml@ f36a666

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 f36a666 was 50633e8, checked in by Mark Hymers <markh@…>, 23 years ago

fixed typo

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

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