From bc362d427414bf9e6990e8f84384f20c3cc7944a Mon Sep 17 00:00:00 2001 From: Jeremy Utley Date: Fri, 12 Sep 2003 06:50:02 +0000 Subject: [PATCH] Corrected problems pointed out on the lists git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2780 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter08/grub.xml | 28 ++++++++++++++++------------ chapter08/introduction.xml | 4 ++-- chapter09/reboot.xml | 20 +------------------- 3 files changed, 19 insertions(+), 33 deletions(-) diff --git a/chapter08/grub.xml b/chapter08/grub.xml index ac135dc52..7c5510b82 100644 --- a/chapter08/grub.xml +++ b/chapter08/grub.xml @@ -9,24 +9,24 @@ we need to ensure we can boot it. To do this, we will run the grub program.Grub uses it's own naming structure for drives, in the form of hd(a,b), where a is the hard drive number, and b is the partition number, both of which -start from zero. So, partition hda1 would be hd(0,0) to grub, and hdb2 would -be hd(1,2). Also, Grub doesn't pay attention to CDROM drives at all, so if, -for example, if you have a CD on hdb, and a second hard drive on hdc, partitions -on that second hard drive would still be hd(1,b). +start from zero. So, partition hda1 would be (hd0,0) to grub, and hdb2 would +be (hd1,1). Also, Grub doesn't pay attention to CDROM drives at all, so if, +for example, you have a CD on hdb, and a second hard drive on hdc, partitions +on that second hard drive would still be (hd1,b). So, using the information above, select the appropriate designator for -your root partition. For the purposes of this, we will assume hd(0,3) for -your root partition. First, we tell grub where to find it's files: +your root partition. For the purposes of this, we will assume (hd0,3) for +your root partition. First, we tell grub where to find its files: root (hd0,3) setup (hd0) quit -This tells grub to look for it's files on hda4 (hd0,3), and install itself +This tells grub to look for its files on hda4 (hd0,3), and install itself into the MBR (Master Boot Record) of hda. Also, we need to create the menu.lst file, which -Grub uses to designate it's boot menu: +Grub uses to designate its boot menu: cat > /boot/grub/menu.lst << "EOF" # Begin /boot/grub/menu.lst @@ -42,7 +42,8 @@ color green/black light-green/black # Default Entry for LFS title LFS 5.0 -kernel (hd0,3)/boot/lfskernel root=/dev/hda4 ro +root (hd0,3) +kernel /boot/lfskernel root=/dev/hda4 ro EOF You might also want to add in an entry for your host distribution. It @@ -51,8 +52,9 @@ might look similar to this: cat >> /boot/grub/menu.lst << "EOF" # Redhat Linux title Redhat -kernel (hd0,2)/boot/kernel-2.4.20 root=/dev/hda3 ro -initrd (hd0,2)/boot/initrd-2.4.20 +root (hd0,2) +kernel /boot/kernel-2.4.20 root=/dev/hda3 ro +initrd /boot/initrd-2.4.20 EOF Also, if you happen to dual-boot Windows, the following entry should @@ -60,7 +62,9 @@ allow booting it: cat >> /boot/grub/menu.lst << "EOF" # Windows -chainloader (hd0,0)+1 +title Windows +rootnoverify (hd0,0) +chainloader +1 EOF You can find more info regarding Grub on it's web site, located at: diff --git a/chapter08/introduction.xml b/chapter08/introduction.xml index 577912223..09a8f8db8 100644 --- a/chapter08/introduction.xml +++ b/chapter08/introduction.xml @@ -4,8 +4,8 @@ This chapter will make LFS bootable. This chapter deals with creating a new fstab file, building a -new kernel for the new LFS system and adding the proper entries to LILO -so that the LFS system can be selected for booting at the LILO: prompt. +new kernel for the new LFS system and installing the Grub bootloader +so that the LFS system can be selected for booting at startup. diff --git a/chapter09/reboot.xml b/chapter09/reboot.xml index b3b53ea3e..a4ab403b5 100644 --- a/chapter09/reboot.xml +++ b/chapter09/reboot.xml @@ -21,29 +21,11 @@ umount $LFS /sbin/shutdown -r now -At the LILO: prompt make sure that you tell it to boot +At the Grub menu make sure that you tell it to boot lfs and not the default entry which will boot your host system again. After you have rebooted, your LFS system is ready for use and you can start adding your own software. -One final thing you may want to do is run lilo, now that you are -booted into LFS. This way you will put the LFS version of LILO in the MBR -rather than the one that's there right now from your host system. -Depending on how old your host distribution is, the LFS version may have -more advanced features you need/could use. - -Either way, run the following to make the lilo version installed -on LFS active: - -/sbin/lilo - -You may now remove the tools directory. If you -think you may need to redo Chapter 5, then you may wish to backup the directory -before removing it. To remove the tools directory, type -the following command, carefully: - -rm -rf /tools -