Changeset e0a04e8 for chapter08/grub.xml


Ignore:
Timestamp:
12/20/2004 06:08:34 PM (19 years ago)
Author:
Manuel Canales Esparcia <manuel@…>
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.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, 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:
1d317bb
Parents:
24244831
Message:

Removed text in chapter 08.

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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter08/grub.xml

    r24244831 re0a04e8  
    1212<secondary>configuring</secondary></indexterm>
    1313
    14 <para>Your shiny new LFS system is almost complete. One of the last things to
    15 do is ensure you can boot it. The instructions below apply only to computers of
    16 IA-32 architecture, meaning mainstream PCs. Information on <quote>boot
    17 loading</quote> for other architectures should be available in the usual
    18 resource-specific locations for those architectures.</para>
    19 
    20 <para>Boot loading can be a complex area. First, a few cautionary words. You
    21 really should be familiar with your current boot loader and any other
    22 operating systems present on your hard drive(s) that you might wish to keep
    23 bootable. Please make sure that you have an emergency boot disk ready, so that
    24 you can rescue your computer if, by any chance, your computer becomes unusable
    25 (un-bootable).</para>
    26 
    27 <para>Earlier, we compiled and installed the Grub boot loader software in
    28 preparation for this step. The procedure involves writing some special Grub
    29 files to specific locations on the hard drive. Before we get to that, we
    30 highly recommend that you create a Grub boot floppy diskette just in case.
     14<para>We highly recommend that you create a Grub boot floppy diskette just in case.
    3115Insert a blank floppy diskette and run the following commands:</para>
    3216
    … …  
    3923<screen><userinput>grub</userinput></screen>
    4024
    41 <para>Grub uses its own naming structure for drives and partitions, in the form
    42 of (hdn,m), where <emphasis>n</emphasis> is the hard drive number, and
    43 <emphasis>m</emphasis> the partition number, both starting from zero. This
    44 means, for instance, that partition <filename class="partition">hda1</filename> is (hd0,0) to
    45 Grub, and <filename class="partition">hdb2</filename> is (hd1,1). In contrast to Linux, Grub
    46 doesn't consider CD-ROM drives to be hard drives, so if you have a CD on
    47 <filename class="partition">hdb</filename>, for example, and a second hard drive on
    48 <filename class="partition">hdc</filename>, that second hard drive would still be (hd1).</para>
    49 
    50 <para>Using the above information, determine the appropriate designator for
    51 your root partition (or boot partition, if you use a separate one). For the
    52 following example, we'll assume your root (or separate boot) partition is
    53 <filename class="partition">hda4</filename>.</para>
    54 
    5525<para>First, tell Grub where to search for its <filename>stage{1,2}</filename>
    5626files -- you can use the Tab key everywhere to make Grub show the alternatives:</para>
    5727
    5828<screen><userinput>root (hd0,3)</userinput></screen>
    59 
    60 
    61 <warning><para>The following command will overwrite your current boot loader.
    62 Don't run the command if this is not what you want. For example, you may be
    63 using a third party boot manager to manage your MBR (Master Boot Record). In
    64 this scenario, it would probably make more sense to install Grub into the
    65 <quote>boot sector</quote> of the LFS partition, in which case this next command
    66 would become: <userinput>setup (hd0,3)</userinput>.</para></warning>
    67 
    6829
    6930<para>Tell Grub to install itself into the MBR (Master Boot Record) of
    … …  
    11778EOF</userinput></screen>
    11879
    119 <para>If <command>info grub</command> doesn't tell you all you want to
    120 know, you can find more information regarding Grub on its website, located at:
    121 <ulink url="http://www.gnu.org/software/grub/"/>.</para>
    122 
    12380<para>The FHS stipulates that Grub's menu.lst file should be symlinked to
    12481/etc/grub/menu.lst.  To satisfy this requirement, issue the following
Note: See TracChangeset for help on using the changeset viewer.