BootX documentation

[David VANTYGHEM]

Perhaps any interesting things in this file ?

https://opensource.apple.com/source/bless/bless-37/README.BOOTING
--
Passez à Linux : https://infolib.re

.--.
|o_o |
||_/ |
// \\ Envoyé depuis mon Linux
(| |)
/ \_ _/ \
\___)=(___/

[John Paul Adrian Glaubitz]

Post by David VANTYGHEM
Perhaps any interesting things in this file ?
https://opensource.apple.com/source/bless/bless-37/README.BOOTING

It does answer some questions, namely about blessing, the tbxi attribute and
the number of backslahes in the OpenFirmware path to be set as boot-device
in NVRAM.

Post by David VANTYGHEM
New World machines (with OF 3.0+) support HFS+, ISO9660, and FAT. When
Mac OS X is installed on an HFS+ volume, BootX is typically placed
in the /System/Library/CoreServices directory, and given the HFS+
type attribute of 'tbxi'. Furthermore, the CoreServices folder is
"blessed", which means that it's directory ID (analogous to an inum
in FFS terminology) is recorded, in the HFS+ volume header.

So, it may or may not be necessary to add the tbxi attribute, depending
on whether one wants to be able to boot the bootloader using the "tbxi"
name.

Post by David VANTYGHEM
The next two components of
boot-device are used to located the BootX secondary loader. The first
("\\") is a special syntax denoting the blessed system folder
mentioned above.

So, what grub-install does here is actually correct, i.e. setting the
path to &device;:&partition;,\\BootX, as "\\" sets the search path to
the blessed folder.

Post by David VANTYGHEM
Because a
directory (and not a file) was specified, ":tbxi" is used to filter
entries that have the HFS+ type of 'tbxi'. If multiple files in the
directory have the same HFS+ type, the first one (in directory order)
is used, which is somewhat non-deterministic from the operating system
point of view, and is not necessarily the alphabetically first entry.
Also, we could
have avoided the filter mechanism and specified the path to BootX
directly. The following forms are all equivalent, and would occur
after the last comma in boot-device variable (assuming the path itself
\\:tbxi
\\BootX
\System\Library\CoreServices\:tbxi
\System\Library\CoreServices\BootX

So, the bootloader installed that way with grub-install should actually
work. My only guess - and that needs to be verified - is that the path
set in OpenFirmware is not correct.

On the other hand, I wonder whether the "tbxi" attribute is actually
necessary for a boot entry to show up in the <<Option>> key menu which
is what we actually want.

Adrian