[plain text]

	<docdate>December 14, 2015</docdate>
		<name><desc>Configuration plist for OS X booter</desc></name>
		<p>The OS X booter (<path>boot.efi</path> on EFI-based Macintosh systems) is responsible for
			loading the initial parts of the operating system into memory and executing them. Its default
			behavior is to start up OS X in graphical mode. However, certain behavior can be
			configured using the <path></path> file, as well as NVRAM variables,
			EFI boot options, and keyboard "snag keys".
		<p>The <path></path> is a standard <manpage>plist<section>5</section></manpage>
			format Core Foundation property list stored in XML format. Keys are generally strings like <command>Kernel Flags</command>,
			with either string or integer values. The following key-values are currently supported:
			<dt><command>Kernel Flags</command></dt><dd>[string] This option specifies arguments to be passed
				directly to the kernel to change its behavior (although some kernel options are parsed by the
				booter as well for correctness). Common options include "debug=0x144" to enable kernel debugging,
				"-v" to enable verbose boot, "-s" to boot to single user mode, "cpus=1" to simulate a
				single core system, and "maxmem=1024" to cap available memory to 1024 MB RAM. All desired options
				should be space-separated within the &lt;string&gt; tag. The default value is the empty string.</dd>
			<dt><command>Kernel Cache</command></dt><dd>[string] This option specifies the prelinked
				kernel file to be loaded, which contains both the kernel and kernel extensions, linked
				at their final load addresses. The path uses backslash ("\") path delimeters. The
				default value is calculated programmatically using
			<dt><command>Root UUID</command></dt><dd>[string] This option is rarely used and specifies
				to the kernel what block device should be probed as the root filesystem ("/"), and is most
				commonly overriden by the OS installation software when installing onto AppleRAID volumes. It can be
				either a filesystem volume UUID, as represented by <command>diskutil info</command>, or
				a GPT partition UUID. The default is generated programmatically based on which filesystem
				the booter itself was loaded from.</dd>
		<p>Since the <path></path> file exists on the root filesystem, it is tied to that 
			OS volume, and is no longer honored if Startup Disk or <manpage>bless<section>8</section></manpage>
			is used to change the boot preference to another volume.
		<p>The <command>Kernel Flags</command> options can also be specified via <arg>--option</arg>
			to <manpage>bless<section>8</section></manpage>, which encodes
			the string in the EFI boot options along with the
			OS boot volume preference. The space-separated strings
			are merged with kernel flags specified in the
			<path></path> and NVRAM.
		<p>At boot time, the booter checks to see if certain keys are being pressed, and alters behavior accordingly.
			This is in addition to similar functionality that the firmware itself may implement before starting the
			booter. Since pressing keys requires physical interaction, they take precendence over preferences
			set through other means, including the <path></path> file and NVRAM.
			The following key combinations are currently supported:
			<dt><command>Shift</command></dt><dd>Boot in Safe Mode. Effectively the same as passing "-x" in
				<command>Kernel Flags</command>, and causes most caches to be ignored by the booter.</dd>
			<dt><command>Command-S</command></dt><dd>Boot in Single User Mode. Effectively the same as passing "-s" in
				<command>Kernel Flags</command>, and causes the system to boot to an interactive shell
				with no system services started.</dd>
			<dt><command>Command-V</command></dt><dd>Boot in Verbose Mode. Effectively the same as passing "-v" in
				<command>Kernel Flags</command>, and causes the system to boot to verbose text logging before
				starting the graphical user interface.</dd>

                        <dt><command>Command-R</command></dt><dd>Boot in Recovery Mode.  This causes the system to boot into special Recovery System image, which can be used to restore the system from Time Machine Backup, re-install OS X, or use Disk Utility to repair or erase disks.</dd>

		<p>The OS X booter can also be controlled by NVRAM variables, which are analogous
			to environment variables. NVRAM variables are key-value pairs. The "boot-args" NVRAM variable
			can be used to provide additional arguments to the kernel, and will be merged with
			<command>Kernel Flags</command> in the <path></path> file and
			EFI boot options set with <manpage>bless<section>8</section></manpage>.
			Since NVRAM variables are system-wide, they are consulted regardless of what OS volume is
			set as the boot preference. NVRAM variables are persistent even when the boot preference
			is changed by Startup Disk or <manpage>bless<section>8</section></manpage>.
		<file>/Library/Preferences/SystemConfiguration/<desc>Location of the <path></path> file.</desc></file>
		<manpage>nvram<section>8</section>, </manpage>
		<manpage>bless<section>8</section>, </manpage>