On 05/05/2019 15:02, Frank Scheiner wrote: > On 5/5/19 14:47, Mark Cave-Ayland wrote: >> On 05/05/2019 13:24, John Paul Adrian Glaubitz wrote: >> >>>> On May 5, 2019, at 2:16 PM, Mark Cave-Ayland >>>> <[email protected]> wrote: >>>> >>>> Presumably for the test ISO image you were manually copying >>>> /System/Library/CoreServices/* into the image yourself? Hopefully with the >>>> above >>>> changes then you should no longer have to do this. >>> >>> No, I used pathspecs and I created the image the exact way that >>> grub-mkrescue does. >>> >>> I think the bootinfo.txt is for IBM CHRP machines while the BootX is for >>> Macs. >> >> Ah no, that's not correct - BootX is an enhanced bootloader written by Apple >> to >> enable multi-booting with MacOS X and grub-mkrescue is assuming that it is >> being >> installed on a HD containing MacOS X with BootX in the default location. > > True, but during installations with `grub-install` that file is > installed there (on disk installations this path is relative to the HFS > bootstrap partition, so `/boot/grub//System/Library/CoreServices/BootX` > is the full path for on-disk installations) anyhow. I think this is to > get GRUB booted via the `mac-boot` command in OF.
Well that's nothing to do with how Macs locate their bootloader - grub-install would have placed the file there because that's how GRUB was configured by the installer. It's not a magic location, simply the one that was specified, and is only relevant if you are installing to a partition containing both MacOS and BootX which is not the case here. ATB, Mark.
