Changeset 968933d for BOOK/bootable/ppc/yaboot.xml

Timestamp:

Jun 3, 2009, 12:23:23 AM (15 years ago)

Author:

Chris Staub <chris@…>

Branches:

clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit

Children:

093b0e8

Parents:

984ac82

Message:

Text updates

File:

• BOOK/bootable/ppc/yaboot.xml (modified) (1 diff)

BOOK/bootable/ppc/yaboot.xml

@@ -29 +29 @@
   in preparation for this step. The procedure involves writing the bootloader
   to a bootstrap partition and blessing it so that Open Firmware will boot from
-  it.  This is all handled by <command>ybin</command> the yaboot installer.</para>
+  it.  This is all handled by <command>ybin</command>, the yaboot installer.</para>
 
   <para os="d">Ybin writes an optional 'OS selector' menu into Open Firmware,
-  then writes yaboot and yaboot.conf to the bootstrap partition, blesses this,
-  and updates the boot device recorded in nvram. When booted, the OF provides
-  the initial menu to choose between linux, boot from CD, and e.g. OSX
-  (depending on what was in yaboot.conf). If you boot to 'linux', yaboot is
-  executed and lets you select which kernel to use.</para>
+  then writes yaboot and <filename>yaboot.conf</filename> to the bootstrap
+  partition, blesses this, and updates the boot device recorded in nvram. When
+  booted, the OF provides the initial menu to choose between linux, boot from
+  CD, and e.g. OSX (depending on what was in <filename>yaboot.conf</filename>).
+  If you boot to 'linux', yaboot is executed and lets you select which kernel
+  to use.</para>
 
   <para os="e">Images (kernels) are specified, together with any necessary path,
-  in yaboot.conf - the details are incorporated into the bootloader, but no attempt
-  is made to access or validate the paths until they are selected.  There are many
-  possible options that can be specified in yaboot.conf, see the man page for the
-  details.  Most people will be able to specify device=hd: (for a single hard disk),
-  but if you have multiple disks, or if you wish to be pedantic, you can specify the
+  in <filename>yaboot.conf</filename> - the details are incorporated into the
+  bootloader, but no attempt is made to access or validate the paths until
+  they are selected. There are many possible options that can be specified in
+  <filename>yaboot.conf</filename>, see the man page for the details. Most
+  people will be able to specify device=hd: (for a single hard disk), but if
+  you have multiple disks, or if you wish to be pedantic, you can specify the
   full OF path to the device, obtained by running <command>ofpath /dev/hdX</command>
   .</para>
 
   <para os="h">Using the above information, determine the appropriate designators
-  for the bootstrap partition and the root partition.  For the following example,
+  for the bootstrap partition and the root partition. For the following example,
   it is assumed that the bootstrap partition is <filename class="partition">hda2
-  </filename> and the root partition is <filename class="partition">hda7</filename>
-  .  We will also assume that you wish to be able to boot an OSX installation on
-  <filename class="partition">hda4</filename>.  Change these items as necessary
+  </filename> and the root partition is <filename class="partition">hda7</filename>.
+  We will also assume that you wish to be able to boot an OSX installation on
+  <filename class="partition">hda4</filename>. Change these items as necessary
   for your machine.</para>
 
   <para os="i">If your machine has a SATA disk, specify the partitions using
   <filename class="devicefile">/dev/sda7</filename> and so forth in the usual
-  way.  At least some of the distros specify a full OF path to the 'device' and
+  way. At least some of the distros specify a full OF path to the 'device' and
   to the image(s), such as
   <parameter>device=/ht@0,f2000000/pci@3/k2-sata-root@c/k2-sata@0/disk@0:</parameter>