+This document is maintained in the upstream yaboot source. Patches +and translations should be sent to erbenson (at) alaska.net. The most +recent sgml version of this document is available via the yaboot rsync +tree: rsync://penguinppc.org/yaboot. +
+The master location of this
+document is
This document is free software; you may redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2, or (at your option) any
@@ -82,7 +92,7 @@ those will require
Be sure you have reviewed the
(Replace xxxx with the starting block number.) A working tarball of a
bootstrap-capable version of mac-fdisk (Debian users already have this
version) is also distributed at
The bootstrap partition only takes 800k of space. If you are adding a
bootstrap partition to your existing setup, you may have enough free
@@ -248,7 +258,7 @@ file must have unix newlines; be sure to save as a unix type file
if you create or edit it within MacOS.
-
For those unfamiliar with Linux device naming, partition paths are in
@@ -263,7 +273,7 @@ represents the partition number. Typical Linux device names are:
hdc secondary controller, master disk (often used for CD-ROM)
hdd secondary controller, slave disk (often used for Zip drive)
sda first SCSI disk (SCSI ID address-wise)
- sdb second SCSI disk
+ sdb second SCSI disk
scd0 first CD-ROM (or sr0)
fd0 first floppy drive
fd1 second floppy drive
@@ -276,8 +286,8 @@ A utility for finding the OpenFirmware device path corresponding to a
given Linux device path is provided:
-For PowerMacs, a magicboot line such as
+For PowerMacs, a magicboot line such as
magicboot=/usr/local/lib/yaboot/ofboot is also required. Several
models cannot execute a straight ELF, and need a CHRP script (which this
line in the
+
If you are setting up a multi-OS boot menu, you'll need to identify the
partitions where each OS lives. You can use Linux-style or OpenFirmware
@@ -365,7 +375,7 @@ assumes it will find the kernel on the same device it was booted from, which
is quite often true. You should always supply the kernel partition number,
for example partition=3, and of course the image path (for example
image=/boot/vmlinux ). If your kernel image is at the root level of
-the parttion, don't forget to include the leading slash when specifying the
+the partition, don't forget to include the leading slash when specifying the
image path (image=vmlinux will probably fail).
@@ -385,7 +395,7 @@ it starts up to let it know where its root filesystem is located. Many other
options are available to pass additional boot parameters to the kernel
(append=), specify initial ramdisk size (ramdisk=), load a
ramdisk image (initrd=), and others. Refer to the yaboot.conf man
-page for details on kernel image options.
+page for details on kernel image options.
@@ -405,7 +415,7 @@ kernel image section:
# How long to wait at the boot: prompt (tenths of a second)
timeout=50
# Globally identified root partition
- root=/dev/hda3
+ root=/dev/hda3
# The device where the kernel lives
device=hd:
@@ -427,12 +437,12 @@ To netboot a kernel image via tftp, use image=/tftpboot/vmlinux (the
path on the tftp server) and device=enet:10.0.0.1
(substituting the tftp boot server IP address).
-
+
Normally the first image specified in the
-Booting password protection is available using a password= line.
+Booting password protection is available using a password= line.
When you add password=, a password will be required for all booting.
Automatic booting is not possible unless a restricted line is added.
@@ -483,8 +493,8 @@ md5 hash use the following perl snippet:
If you have a problem booting, don't panic. Yaboot can boot any
-installed Linux kernel and system from the boot: prompt.
+installed Linux kernel and system from the boot: prompt.
@@ -565,12 +575,12 @@ resolution will also be reset to their defaults.
If a boot: prompt isn't presented, then
@@ -581,7 +591,7 @@ boot command to directly boot your kernel.
-The full OpenFirmware path consists of three parts in the format
+The full OpenFirmware path consists of three parts in the format
@@ -618,7 +628,7 @@ Hit return, and
Once you have the boot: prompt, you can enter a label defined in your
@@ -632,14 +642,14 @@ you can enter a full OpenFirmware path. A typical kernel path might be
To pass parameters to the kernel, add them on to the boot: prompt
line after the kernel label or path. You'll need to specify root=
as a minimum, but you can add any kernel parameters desired. Here's an
-example;
+example;
It's very convenient for certain tasks like installing a new system
the first time without a CD, or rescuing an existing system, to boot a
@@ -656,7 +666,7 @@ are placed at the root level on an existing partition.
-The
+You must pick a partition that is formatted with either HFS or HFS+. If
+you have Mac OS X installed on a UFS partition (You can use the OS X "Disk
+Utility" app to check this), you will have to find another partition to use.
+If Mac OS X is installed on UFS, you probably have one or two partitions
+of the "Apple_Boot" type. They have HFS filesystems on them. Pick one,
+mount it under MacOS X, and store the files there.
+
Boot into OpenFirmware, and type at the prompt:
How do I install Debian?
-
-