1 <!DOCTYPE debiandoc PUBLIC "-//DebianDoc//DTD DebianDoc//EN" [
4 file, directory, device == file
5 program, command == prgn
9 key input == em, example for longer ones
18 HOWTO-Booting with Yaboot on PowerPC
21 <name>Chris Tillman</name>
23 <version>Version 1.04, Feb 22 2004</version>
25 This document contains installation and usage instructions for
26 <prgn>yaboot</prgn>, the GNU/Linux PowerPC bootloader.
30 This document may be distributed and modified under the terms of the
31 GNU General Public License.
32 © 1998–2002 Chris Tillman
35 This document is maintained in the upstream yaboot source. Patches
36 and translations should be sent to erbenson (at) alaska.net. The most
37 recent sgml version of this document is available via the yaboot rsync
38 tree: rsync://penguinppc.org/yaboot.
40 The master location of this
42 id="http://penguinppc.org/bootloaders/yaboot/doc/yaboot-howto.shtml"
43 name="http://penguinppc.org/bootloaders/yaboot/doc/yaboot-howto.shtml">.
45 This document is free software; you may redistribute it and/or modify it
46 under the terms of the GNU General Public License as published by the
47 Free Software Foundation; either version 2, or (at your option) any
50 This document is distributed in the hope that it will be useful, but
51 <em>without any warranty</em>; without even the implied warranty of
52 merchantability or fitness for a particular purpose. See the GNU
53 General Public License for more details.
56 A copy of the GNU General Public License is available as
57 <file>/usr/share/common-licenses/GPL</file> in the Debian GNU/Linux
58 distribution or on the World Wide Web at the <url
59 id="http://www.gnu.org/copyleft/gpl.html" name="GNU website">. You can also
60 obtain it by writing to the Free Software Foundation, Inc., 59 Temple Place
61 - Suite 330, Boston, MA 02111-1307, USA.
64 <chapt>Yaboot's Purpose
67 Yaboot is a bootloader for PowerPC computers (NewWorld PowerMacs and IBM
68 CHRP). It loads a Linux operating system kernel from an
69 OpenFirmware-accessible filesystem and initiates operation of the kernel. On
70 PowerMacs, an included CHRP script can display a multi-OS boot menu which
71 can launch <prgn>yaboot</prgn> or other operating systems. Utilities are
72 included to place <prgn>yaboot</prgn> and the associated script on a
73 non-mountable bootstrap partition.
76 <chapt>System Requirements
78 Motorola PowerPC processors have been used on at least three different
79 kinds of systems: NuBus, OldWorld PCI, and NewWorld PCI. Nubus systems
80 include the 6100/7100/8100 line of Power Macintoshes. OldWorld systems
81 are most Power Macintoshes with a floppy drive and a PCI bus. Most
82 603, 603e, 604, and 604e based Power Macintoshes, including the 7200,
83 7300, 7500, 7600, 8500, 8600, 9500, and 9600 are OldWorld
84 machines. The beige colored G3 systems are also OldWorld.
87 <em><prgn>yaboot</prgn> will not work on NuBus or OldWorld machines</em>,
88 those will require <prgn>quik</prgn> or (for MacOS Pre-9.0.4 only)
89 <prgn>BootX/miboot</prgn>.
92 The NewWorld PowerMacs, for which <prgn>yaboot</prgn> is designed, are
93 any PowerMacs in translucent colored plastic cases. That includes all
94 iMacs, iBooks, G4 systems, blue colored G3 systems, and most
95 PowerBooks manufactured in and after 1999.
98 <chapt>Obtaining Yaboot
101 Yaboot is included with Debian GNU/Linux installation for PowerPC computers.
102 Updates for Debian may be downloaded via the normal methods, such as
103 <prgn>apt-get</prgn>, <prgn>dselect</prgn>, or <prgn>dpkg</prgn>.
104 Installation of an updated version of <prgn>yaboot</prgn> on your system
105 does not change your boot configuration; you must use the included
106 <prgn>ybin</prgn> utility to do that.
110 You can also download <prgn>yaboot</prgn> directly from the
111 <prgn>yaboot</prgn> home page at <url
112 id="http://penguinppc.org/bootloaders/yaboot/">. If you download it using MacOS,
113 be sure to download using <em>binary</em> (not text) format, and don't let
114 Stuffit Expander or another utility expand the archive in MacOS.
118 You can download the precompiled <file>yaboot-binary-X.Y.tar.gz</file>, or
119 the source tarball <file>yaboot-X.Y.tar.gz</file>. To unpack the binary
120 distribution, use the command <tt>tar -zxvpf yaboot-X.Y.tar.gz</tt>. The
121 components are unpacked into a <file>usr/local/</file> directory inside the
122 directory where the command was executed.
126 To make and install from source, first make sure you have a working compiler
127 (<prgn>gcc</prgn>) and the <prgn>make</prgn> program installed. (If
128 not, download the binary yaboot tarball instead of the source.) Then run the
129 following commands (substitute the actual revision numbers for X and Y):
133 tar -zxvpf yaboot-X.Y.tar.gz
140 <chapt>Creating the Bootstrap Partition
143 Be sure you have reviewed the <prgn>mac-fdisk</prgn> Basics page at <url
144 id="http://penguinppc.org/bootloaders/yaboot/doc/mac-fdisk-basics.shtml">. If
145 you are creating a new Linux installation, the first partition you create
146 with <prgn>mac-fdisk</prgn> should be the bootstrap partition. Just use the
147 <prgn>mac-fdisk</prgn> <tt>b</tt> command to automatically create a
148 bootstrap partition of the proper size and type. If your version of
149 <prgn>mac-fdisk</prgn> doesn't include the <tt>b</tt> command, use:
153 Command (? for help): C xxxx 800k bootstrap Apple_Bootstrap
157 (Replace xxxx with the starting block number.) A working tarball of a
158 bootstrap-capable version of mac-fdisk (Debian users already have this
159 version) is also distributed at <url
160 id="http://penguinppc.org/~eb/files/">. To install this, use
165 gzip -dc mac-fdisk.tar.gz | tar -xvp
169 The bootstrap partition only takes 800k of space. If you are adding a
170 bootstrap partition to your existing setup, you may have enough free
171 space on your existing drive without changing other partitions. If
172 not, you could avoid re-partitioning the entire disk by stealing a
173 little space from your swap partition. Or <prgn>parted</prgn> would allow
174 you to resize partitions.
178 The bootstrap partition should end up being partition #2, after the
179 partition map itself but before any other partitions on the disk. You can
180 easily change the order of the partitions in the partition map using the
181 <tt>r</tt> command (see the <prgn>mac-fdisk</prgn> tutorial). In other
182 words, it's not the physical placement of the bootstrap partition that
183 counts, it's the logical order within the partition map. Note, though, if
184 you have an existing system and you shift the partition numbers around, you
185 will need to make the appropriate changes in <file>/etc/fstab</file>.
189 The reason you want the bootstrap partition as partition #2, is so
190 that it precedes all other partitions in the boot sequence. This helps
191 tremendously to make the entire system more stable, since some OS's
192 are very intrusive in their use of partitions.
196 When you're finished partitioning, use the <tt>p</tt> command and make note
197 of the final partition numbers. You will need to know the partition
198 number for the bootstrap partition, the location of your kernel, and
199 if you intend to set up <prgn>yaboot</prgn> for multiple OS booting, partition
200 numbers for your alternate OS's.
204 While it's possible to install <prgn>yaboot</prgn> on a mountable HFS
205 <file>/boot</file> partition, that configuration is deprecated, discouraged
206 and completely unsupported.
208 <chapt>Yabootconfig: Make It Easy
211 For initial installation on a machine, you can use <prgn>yabootconfig</prgn>
212 to first create a <file>yaboot.conf</file> file and then install everything
213 on your bootstrap partition. Yabootconfig reads the running system's
214 <file>/etc/fstab</file> to determine the kernel location, and detects the
215 location of the 800k Apple_Bootstrap partition. The Debian installer uses
216 <prgn>yabootconfig</prgn> behind the scenes in the Make Hard Disk Bootable
221 Normally, the initial boot configuration is created while in a ramdisk
222 installer environment, with the system being installed being mounted under
223 <file>/target</file> or <file>/mnt</file>. To run <prgn>yabootconfig</prgn>
224 under these conditions, supply the path to the target system with -t or
225 --chroot option. For example: <tt>yabootconfig --chroot /target</tt>
229 The <file>yaboot.conf</file> automatically created by
230 <prgn>yabootconfig</prgn> will just control booting of the linux system
231 under which it was created. To boot additional OS's or add other options,
232 you will need to edit the <file>yaboot.conf</file> file.
235 <chapt>Customizing Your Boot Configuration
238 To customize your <prgn>yaboot</prgn> installation, use any text editor such
239 as <prgn>vi</prgn> or <prgn>nano</prgn> (or <prgn>nano-tiny</prgn> in the
240 Debian installer) to edit the <file>yaboot.conf</file> file. If you used
241 <prgn>yabootconfig</prgn> to create the initial <file>yaboot.conf</file>, it
242 will already contain a basic configuration to boot the linux system.
246 The <file>yaboot.conf</file> has numerous options; see the
247 <file>yaboot.conf</file> man page for details. I will briefly cover the most
248 popular items here. The file controls both <prgn>yaboot</prgn> operation
249 during tha actual boot, and <prgn>ybin</prgn> operation while saving the
250 configuration to the boot partition.
254 Lines in the file beginning with <tt>#</tt> are interpreted as comments. Each
255 option or parameter must be specified on a separate line. Don't use
256 any extra spaces within or following parameter definitions. Also, the
257 file must have unix newlines; be sure to save as a unix type file
258 if you create or edit it within MacOS.
261 <sect>Linux Style Device Paths
264 For those unfamiliar with Linux device naming, partition paths are in
265 the form of <tt>/dev/xxx#</tt> where xxx is the Linux device name and #
266 represents the partition number. Typical Linux device names are:
270 ---- --------------------------------------------------
271 hda internal ide drive (primary controller, master disk)
272 hdb internal ide drive (primary controller, slave disk)
273 hdc secondary controller, master disk (often used for CD-ROM)
274 hdd secondary controller, slave disk (often used for Zip drive)
275 sda first SCSI disk (SCSI ID address-wise)
277 scd0 first CD-ROM (or sr0)
278 fd0 first floppy drive
279 fd1 second floppy drive
283 <sect>OpenFirmware Device Paths
285 A utility for finding the OpenFirmware device path corresponding to a
286 given Linux device path is provided: <prgn>ofpath</prgn>. <prgn>ybin</prgn>
287 uses <prgn>ofpath</prgn>
288 internally to convert Linux device names you use in <file>yaboot.conf</file> to
289 OpenFirmware equivalents. Example: <tt>ofpath /dev/hda</tt> (should return hd:).
290 You can also figure out OpenFirmware device paths yourself, see
291 Recovering From Misconfiguration below.
293 <sect>Required Settings
296 The bootstrap partition is identified with <tt>boot=boot-partition</tt>,
297 where boot-partition is the Linux-style path to the bootstrap partition. If
298 you followed our partitioning recommendations on your internal hard disk,
299 that would be <tt>boot=/dev/hda2</tt>.
303 For PowerMacs, a magicboot line such as
304 <tt>magicboot=/usr/local/lib/yaboot/ofboot</tt> is also required. Several
305 models cannot execute a straight ELF, and need a CHRP script (which this
306 line in the <file>yaboot.conf</file> makes available).
310 The <tt>partition=</tt>, <tt>image=</tt>, and <tt>root=</tt> settings (under
311 kernel image settings below) are also required.
313 <sect>Boot Menu Options
316 A CHRP script (<file>ofboot</file>) has been provided which
317 <prgn>ybin</prgn> will modify using <file>yaboot.conf</file> settings, to
318 display a very handy multi-OS boot menu.
322 If you are setting up a multi-OS boot menu, you'll need to identify the
323 partitions where each OS lives. You can use Linux-style or OpenFirmware
324 partition paths. Here are some examples illustrating the possibilities:
333 When using <tt>macosx=</tt>, if you have OSX installed on a UFS partition,
334 then point the macosx to the OSX bootstrap partition, not the UFS root.
335 Don't be tempted to use the OSX bootstrap partition for <prgn>ybin</prgn>,
336 however — you still need a separate Apple_Bootstrap partition.
340 When using <tt>bsd=</tt>, on the other hand, point to the BSD root
341 partition, not a bsd bootstrap partition. To use <tt>bsd=</tt>, you also
342 need to have the bsd bootloader (ofwboot) available in
343 <file>/usr/local/lib/yaboot/</file> when running <prgn>ybin</prgn>.
347 If nothing is selected from the boot menu when it appears, the system
348 launches <prgn>yaboot</prgn> to start Linux. To launch another OS when no
349 key is pressed, add a <tt>defaultos=</tt> line, for example
350 <tt>defaultos=macos</tt> or <tt>defaultos=bsd</tt>.
353 <sect>Kernel Image Settings
355 Kernel images to be launched by yaboot can be kept on any partition,
356 in an ext2, ext3, XFS, ReiserFS, or HFS/HFS+ filesystem. Yaboot will
357 need to know the kernel partition number and filesystem path.
361 The <file>yaboot.conf</file> file has two sections; most options are in the
362 global section at the top of the file, and options pertaining to separate
363 kernel images are grouped together below. Most kernel image options may be
364 specified either globally or locally; a global option is overridden if it is
365 re-specified in a kernel image section. Each kernel image section begins
366 with an <tt>image=/</tt> line specifying the filesystem path to that kernel
367 image; the first <tt>image=/</tt> line marks the end of the global section.
371 Yaboot must know the device, partition number, and filesystem path for the
372 kernel image that is to be loaded and started. However, <tt>device=</tt> is
373 usually not necessary, because if you don't specify it <prgn>yaboot</prgn>
374 assumes it will find the kernel on the same device it was booted from, which
375 is quite often true. You should always supply the kernel partition number,
376 for example <tt>partition=3</tt>, and of course the image path (for example
377 <tt>image=/boot/vmlinux</tt> ). If your kernel image is at the root level of
378 the partition, don't forget to include the leading slash when specifying the
379 image path (<tt>image=vmlinux</tt> will probably fail).
383 It's worth noting that <prgn>yaboot</prgn> locates the kernel image within a
384 partition's filesystem without regard to where that partition will
385 eventually be mounted within the Linux root filesystem. So, for example, if
386 you've placed a kernel image or symlink at /boot/vmlinux, but /boot is
387 actually a separate partition on your system, then the image path for
388 <prgn>yaboot</prgn> will just be <tt>image=/vmlinux</tt>.
392 You must also specify the Linux partition path for the root partition, for
393 example <tt>root=/dev/hda3</tt>. This parameter is passed to the kernel when
394 it starts up to let it know where its root filesystem is located. Many other
395 options are available to pass additional boot parameters to the kernel
396 (<tt>append=</tt>), specify initial ramdisk size (<tt>ramdisk=</tt>), load a
397 ramdisk image (<tt>initrd=</tt>), and others. Refer to the yaboot.conf man
398 page for details on kernel image options.
402 Here's a simple but complete example <file>yaboot.conf</file> with one
403 kernel image section:
406 # Where's the bootstrap partition
409 magicboot=/usr/lib/yaboot/ofboot
410 # Dual boot with MacOS
412 # How long to wait at the OS boot menu (seconds)
415 # How long to wait at the boot: prompt (tenths of a second)
417 # Globally identified root partition
419 # The device where the kernel lives
422 # Kernel image section begins here
423 # Specify the filesystem path to the kernel image, symlinks are OK
425 # Specify the partition number where this path is valid
427 # Add a label, you can type this at the boot: prompt to load this kernel
429 # Specify the type of root fs mounting, read-only allows fsck to run
432 ## You must run ybin for changes to take effect!!!!!!!
436 To netboot a kernel image via tftp, use <tt>image=/tftpboot/vmlinux</tt> (the
437 path on the tftp server) and <tt>device=enet:10.0.0.1</tt>
438 (substituting the tftp boot server IP address).
442 Normally the first image specified in the <file>yaboot.conf</file> will be the
443 image booted if no entry is made at the boot: prompt. To have another
444 image loaded by default, add a <tt>default=label</tt> line in the global
448 <sect>Optional and Cool Settings
451 Yaboot and your multiboot menu can throw a splash of color into your life!
452 Use <tt>fgcolor=</tt> and <tt>bgcolor=</tt> lines to set your screen to wake
453 you up in the morning with black, blue, light-blue, green, light-green,
454 cyan, light-cyan, red, light-red, purple, light-purple, brown, light-gray,
455 dark-gray, yellow, and white. Make fgcolor and bgcolor the same if you'd
456 really like a challenge.
460 Add any or all of enableofboot, enablenetboot, or enablecdboot to add
461 the respective options to your OS boot menu: boot from OpenFirmware,
462 the network, or CDROM.
466 Use Set delay= (in seconds) to determine how long the multiboot OS menu
467 should wait before booting the default OS. <tt>timeout=</tt> (in tenths of
468 seconds) to set how long yaboot should wait at the boot: prompt for
469 you to choose a kernel image before booting the first image in the
470 file or the <tt>default=</tt> image.
474 Booting password protection is available using a <tt>password=</tt> line.
475 When you add <tt>password=</tt>, a password will be required for all booting.
476 Automatic booting is not possible unless a <tt>restricted</tt> line is added.
480 If <tt>restricted</tt> is added in the global section, kernel images defined
481 in <file>yaboot.conf</file> may be booted as long as no arguments are added
482 at the boot: prompt. This is useful for unattended booting, while preventing
483 the instant rootshell problems of console access (though OpenFirmare
484 passwords are also needed to make this really secure, along with locking the
485 case). To boot an undefined image, or any image with additional arguments, a
486 password will be required.
490 The <tt>password=</tt> line may either be a plaintext password or an MD5
491 hash (the same format as the Linux <file>/etc/shadow</file> file). To make an
492 md5 hash use the following perl snippet:
495 $ perl -e 'printf("%s\n", crypt("secret", "\$1\$saltstrg"))'
497 The saltstrg should be a random string, for example one generated by
504 <chapt>Saving Boot Configuration Changes
507 There are currently three utilities provided to save your boot configuration
508 changes to the boot partition: <prgn>ybin</prgn>, <prgn>mkofboot</prgn>, and
509 <prgn>yabootconfig</prgn>. Ybin copies <prgn>yaboot</prgn>,
510 <file>yaboot.conf</file>, and the CHRP script to the boot partition, and
511 then performs the necessary blessing. Mkofboot initializes the bootstrap
512 partition, then runs <prgn>ybin</prgn>. And <prgn>yabootconfig</prgn>
513 creates a working <file>yaboot.conf</file> and then runs
514 <prgn>mkofboot</prgn>. For details and options of these utilities, see the
515 associated man pages or type the utility name followed by --help on the
519 <chapt>Common Mistakes
522 The most common mistake made in the usage of <prgn>yaboot</prgn> is trying
523 to use it to boot from a mountable partition on a permanent basis. When a
524 PowerPC first starts up, the booting process is started by locating a
525 so-called `blessed' folder. The MacOS places the blessing so that multiple
526 system folders may exist on a partition, but only one of them will be valid
527 for starting up. If the computer is set up to dual boot Linux and MacOS,
528 when MacOS is booted it will unbless any folders which do not contain a
529 valid MacOS system. Then the next time the machine boots, the partition
530 containing the formerly blessed folder will not be bootable.
534 The utilities provided with <prgn>yaboot</prgn> should always be used to set
535 it up on its own bootstrap partition for regular booting needs. The only
536 time you should place <prgn>yaboot</prgn> on a mountable partition is for
537 initial installation of Linux and rescue operations. In those cases you can
538 intervene in the normal bootloading process to request a specific file to be
539 executed, and blessed folders are not an issue since this type of booting is
544 After <prgn>yaboot</prgn> has been installed, another common mistake is
545 changing the boot configuration file or updating the <prgn>yaboot</prgn>
546 software and then failing to re-run the <prgn>ybin</prgn> utility to
547 transfer the changed configuration to the boot partition. Booting functions
548 will not be changed unless the changes are saved to the bootstrap partition.
549 If you change your <file>yaboot.conf</file> often, you might want to add a
550 comment line inside the <file>yaboot.conf</file> file to remind yourself to
551 run <prgn>ybin</prgn> after making changes.
554 <chapt>Recovering From Misconfiguration
557 If you have a problem booting, don't panic. Yaboot can boot any
558 installed Linux kernel and system from the boot: prompt.
560 <sect>Resetting the NVRAM
563 Hold the Command-Option-p-r keys all together at startup to reset all nvram
564 parameters to their factory defaults. Hold the keys until you hear the
565 startup chime two or three times. If the setup recommendations were
566 followed, the <prgn>yaboot</prgn> installation will be be the first bootable
567 partition and OpenFirmware will boot it automatically. It should be noted
568 that MacOS settings such as virtual memory, startup disk, and screen
569 resolution will also be reset to their defaults.
575 If a <tt>boot:</tt> prompt isn't presented, then <prgn>yaboot</prgn> isn't
576 being loaded. You can load it manually from
577 OpenFirmware. Holding the Command-Option-o-f keys all together after
578 pressing the power-on key will give you an OpenFirmware prompt
583 (Command is the key with the cloverleaf and/or apple engraved on it).
587 At the OF prompt, you will need to use OpenFirmware paths for most of
588 the boot configuration items. You can determine most OpenFirmware
589 paths from the OF prompt using a few OF commands, then construct an OF
590 boot command to directly boot your kernel.
594 The full OpenFirmware path consists of three parts in the format
597 device-name:partition-number,/filesystem-path
602 The OF command devalias will list all the device aliases effective on
603 your system. You may see some of these:
606 ---- --------------------------------------------------
607 hd internal ide drive (primary controller, master disk)
608 ultra1 internal ide drive (primary controller, slave disk)
609 ide0 ide drive (secondary controller, master disk)
610 ide1 ide drive (secondary controller, slave disk)
613 fw FireWire interface
615 enet Ethernet interface
618 Append the partition number of the boot partition (in our recommendation, 2)
619 and then follow that with <tt>,yaboot</tt> to boot the <prgn>yaboot</prgn>
620 file on the boot partition.
627 Hit return, and <prgn>yaboot</prgn> should be loaded and display its
628 <file>boot:</file> prompt. If you don't know the partition number, just
629 start at 2 and work your way up until you hit it.
631 <sect>Manually Loading a Kernel Image
634 Once you have the boot: prompt, you can enter a label defined in your
635 <file>yaboot.conf</file> to boot that kernel image. Or instead of a label,
636 you can enter a full OpenFirmware path. A typical kernel path might be
642 To pass parameters to the kernel, add them on to the <tt>boot:</tt> prompt
643 line after the kernel label or path. You'll need to specify <tt>root=</tt>
644 as a minimum, but you can add any kernel parameters desired. Here's an
648 boot: hd:3,/vmlinux root=/dev/hda3 ro
652 <chapt>Yaboot as a Temporary Bootloader
654 It's very convenient for certain tasks like installing a new system
655 the first time without a CD, or rescuing an existing system, to boot a
656 ramdisk system such as an installer directly from files placed on an
661 An example is the Debian installer. It is contained in a floppy-image
662 root.bin file which <prgn>yaboot</prgn> can boot directly. A simple
663 <file>yaboot.conf</file> to initialize the ramdisk, yaboot, root.bin, and a
664 kernel image (named linux in this example) are all that is needed. All files
665 are placed at the root level on an existing partition.
669 The <file>yaboot.conf</file> file for this purpose contains just
679 If you create <file>yaboot.conf</file> in the MacOS, you must convert
680 it to use Unix newlines (linefeeds only). If you use MacOS newlines
681 (just carriage returns), <prgn>yaboot</prgn> will be unable to read the file.
684 You must pick a partition that is formatted with either HFS or HFS+. If
685 you have Mac OS X installed on a UFS partition (You can use the OS X "Disk
686 Utility" app to check this), you will have to find another partition to use.
687 If Mac OS X is installed on UFS, you probably have one or two partitions
688 of the "Apple_Boot" type. They have HFS filesystems on them. Pick one,
689 mount it under MacOS X, and store the files there.
692 Boot into OpenFirmware, and type at the prompt:
694 0 > boot hd:xx,yaboot
697 replacing xx with the partition number of the partition where the
698 kernel and <prgn>yaboot</prgn> files were placed, followed by a return. At the
699 boot: prompt, type <em>install</em> followed by a return.
702 <chapt>For More Information
707 <item> <url id="http://penguinppc.org/bootloaders/yaboot/" name="Yaboot Home">
712 How do I install Debian?
714 <item> <url id="http://www.debian.org/releases/woody/powerpc/install"
715 name="Installing Debian GNU/Linux 3.0 For PowerPC">
720 What's Open Firmware?
722 <item> <url id="http://developer.apple.com/technotes/tn/tn1044.html">
723 <item> <url id="http://developer.apple.com/technotes/tn/tn1061.html">
724 <item> <url id="http://developer.apple.com/technotes/tn/tn1062.html">
725 <item> <url id="http://developer.apple.com/technotes/tn/tn1167.html">
734 <!-- Keep this comment at the end of the file
739 sgml-namecase-general:t
740 sgml-general-insert-case:lower
741 sgml-minimize-attributes:max
742 sgml-always-quote-attributes:t
745 sgml-parent-document:nil
747 sgml-exposed-tags:nil
748 sgml-local-catalogs:nil
749 sgml-local-ecat-files:nil