Changeset bc362d4
- Timestamp:
- 09/12/2003 06:50:02 AM (21 years ago)
- 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, 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:
- 03bdafe
- Parents:
- b46ab4c
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/grub.xml
rb46ab4c rbc362d4 10 10 <para>Grub uses it's own naming structure for drives, in the form of hd(a,b), 11 11 where a is the hard drive number, and b is the partition number, both of which 12 start from zero. So, partition hda1 would be hd(0,0) to grub, and hdb2 would13 be hd(1,2). Also, Grub doesn't pay attention to CDROM drives at all, so if,14 for example, ifyou have a CD on hdb, and a second hard drive on hdc, partitions15 on that second hard drive would still be hd(1,b).</para>12 start from zero. So, partition hda1 would be (hd0,0) to grub, and hdb2 would 13 be (hd1,1). Also, Grub doesn't pay attention to CDROM drives at all, so if, 14 for example, you have a CD on hdb, and a second hard drive on hdc, partitions 15 on that second hard drive would still be (hd1,b).</para> 16 16 17 17 <para>So, using the information above, select the appropriate designator for 18 your root partition. For the purposes of this, we will assume hd(0,3) for19 your root partition. First, we tell grub where to find it 's files:</para>18 your root partition. For the purposes of this, we will assume (hd0,3) for 19 your root partition. First, we tell grub where to find its files:</para> 20 20 21 21 <para><screen><userinput>root (hd0,3) … … 23 23 quit</userinput></screen></para> 24 24 25 <para>This tells grub to look for it 's files on hda4 (hd0,3), and install itself25 <para>This tells grub to look for its files on hda4 (hd0,3), and install itself 26 26 into the MBR (Master Boot Record) of hda.</para> 27 27 28 28 <para>Also, we need to create the <filename>menu.lst</filename> file, which 29 Grub uses to designate it 's boot menu:</para>29 Grub uses to designate its boot menu:</para> 30 30 31 31 <para><screen><userinput>cat > /boot/grub/menu.lst << "EOF" … … 43 43 # Default Entry for LFS 44 44 title LFS 5.0 45 kernel (hd0,3)/boot/lfskernel root=/dev/hda4 ro 45 root (hd0,3) 46 kernel /boot/lfskernel root=/dev/hda4 ro 46 47 EOF</userinput></screen></para> 47 48 … … 52 53 # Redhat Linux 53 54 title Redhat 54 kernel (hd0,2)/boot/kernel-2.4.20 root=/dev/hda3 ro 55 initrd (hd0,2)/boot/initrd-2.4.20 55 root (hd0,2) 56 kernel /boot/kernel-2.4.20 root=/dev/hda3 ro 57 initrd /boot/initrd-2.4.20 56 58 EOF</userinput></screen></para> 57 59 … … 61 63 <para><screen><userinput>cat >> /boot/grub/menu.lst << "EOF" 62 64 # Windows 63 chainloader (hd0,0)+1 65 title Windows 66 rootnoverify (hd0,0) 67 chainloader +1 64 68 EOF</userinput></screen></para> 65 69 -
chapter08/introduction.xml
rb46ab4c rbc362d4 5 5 <para>This chapter will make LFS bootable. This chapter deals with creating a 6 6 new fstab file, building a 7 new kernel for the new LFS system and adding the proper entries to LILO8 so that the LFS system can be selected for booting at the LILO: prompt.</para>7 new kernel for the new LFS system and installing the Grub bootloader 8 so that the LFS system can be selected for booting at startup.</para> 9 9 10 10 </sect1> -
chapter09/reboot.xml
rb46ab4c rbc362d4 22 22 <para><screen><userinput>/sbin/shutdown -r now</userinput></screen></para> 23 23 24 <para>At the LILO: promptmake sure that you tell it to boot24 <para>At the Grub menu make sure that you tell it to boot 25 25 <emphasis>lfs</emphasis> and not the default entry which will boot your 26 26 host system again.</para> … … 29 29 can start adding your own software.</para> 30 30 31 <para>One final thing you may want to do is run lilo, now that you are32 booted into LFS. This way you will put the LFS version of LILO in the MBR33 rather than the one that's there right now from your host system.34 Depending on how old your host distribution is, the LFS version may have35 more advanced features you need/could use.</para>36 37 <para>Either way, run the following to make the lilo version installed38 on LFS active:</para>39 40 <para><screen><userinput>/sbin/lilo</userinput></screen></para>41 42 <para>You may now remove the <filename>tools</filename> directory. If you43 think you may need to redo Chapter 5, then you may wish to backup the directory44 before removing it. To remove the <filename>tools</filename> directory, type45 the following command, carefully:</para>46 47 <para><screen><userinput>rm -rf /tools</userinput></screen></para>48 49 31 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.