Changeset bd709ec for BOOK/bootable

May 10, 2006, 4:36:40 PM (14 years ago)
Jim Gifford <clfs@…>
clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit

r3373@server (orig r1556): ken | 2006-05-10 15:15:06 -0700
Improve yaboot.conf and add examples of sata paths, drop reference to pegasos ppc for lack of information, and correct my attempts to spell Open Firmware as one word.

1 edited


  • BOOK/bootable/ppc/yaboot.xml

    rfadf920 rbd709ec  
    1717  <para os="a">Your shiny new LFS system is almost complete. One of the last
    1818  things to do is to ensure that the system can be properly booted. The
    19   instructions below apply only to NewWorld Macintoshes and (probably)
    20   PegasosPPC.</para>
     19  instructions below apply only to NewWorld Macintoshes.</para>
    2221  <para os="b">Boot loading can be a complex area, so a few cautionary words
    2423  operating systems present on the hard drive(s) that need to be bootable.
    2524  Make sure that an emergency CD is ready to <quote>rescue</quote> the
    26   computer if it becomes un-bootable.</para>
     25  computer if it becomes un-bootable.  It is also a good idea to enable booting
     26  from Open Firmware in case things go really wrong.</para>
    2828  <para os="c">Earlier, we compiled and installed the yaboot boot loader software
    2929  in preparation for this step. The procedure involves writing the bootloader
    30   to a bootstrap partition and blessing it so that OpenFirmware will boot from
    31   it.  This is all handled by <command>ybin</command> the yaboot installer.</para> 
     30  to a bootstrap partition and blessing it so that Open Firmware will boot from
     31  it.  This is all handled by <command>ybin</command> the yaboot installer.</para>
    3333  <para os="d">Ybin assembles all the information it needs by reading yaboot.conf,
    4242  details.  Most people will be able to specify device=hd: (for a single hard disk),
    4343  but if you have multiple disks, or if you wish to be pedantic, you can specify the
    44   full OF path to the device, obtained by running <command>ofpath</command>.</para>
     44  full OF path to the device, obtained by running <command>ofpath /dev/hdX</command>
     45  .</para>
    4647  <para os="f">Note that the man page mentions which filesystems yaboot can
    5758  <filename class="partition">hda4</filename>.  Change these items as necessary
    5859  for your machine.</para>
     61  <para os="i">If your machine has a SATA disk, specify the partitions using
     62  <filename class="devicefile">/dev/sda7</filename> and so forth in the usual
     63  way.  At least some of the distros specify a full OF path to the 'device' and
     64  to the image(s), such as
     65  <filename class="devicefile">device=/ht@0,f2000000/pci@3/k2-sata-root@c/k2-sata@0/disk@0:
     66  </filename> for the disk, and
     67  <filename class="partition">image=/ht@0,f2000000/pci@3/k2-sata-root@c/k2-sata@0/disk@0:9,/boot/lfskernel-&linux-version;
     68  </filename> which definitely works.</para>
    6070  <para os="k">Create a <quote>yaboot.conf</quote> file defining yaboot's boot
     102# allow the initial menu to offer booting from Open Firmware
    92105# allow the initial menu to boot from mac osx
     108# white on black is boring!
     109# note  the spellings : 'fgcolor' but 'light'
     110# in this context, light means 'without high intensity'
    95113# The first entry is for LFS.
    96114# For all images, the pathname is relative to the filesystem
    97 # on which they are mounted.
     115# on which they are situated and can include at most one
     116# directory
    99118    label=&version;
Note: See TracChangeset for help on using the changeset viewer.