Re: [PATCH] bless command

[Vladimir 'phcoder' Serbinenko]

On Sat, Aug 29, 2009 at 9:58 AM, Michal Suchanek<address@hidden> wrote:
> 2009/8/29 Bean <address@hidden>:
>> On Sat, Aug 29, 2009 at 2:27 PM, Vladimir 'phcoder'
>> Serbinenko<address@hidden> wrote:
>>>> Actually, I think the correct handling is to first bless a boot
>>>> directory (storing the directory id in header), then bless a boot file
>>>> (add +tbxi attribute), that's why the bless command in OSX needs needs
>>>> both --folder and --file option.
>>> AFAIK --file has no effect for intel macs.
>>
>> Hi,
>>
>> After more testing, I believe the booting process works like this:
>>
>> One important difference between openfirmware and efi is that
>> openfirmware stores file path in nvram, while efi stores device path.
>> The default boot file for openfirmware is like this:
>>
>> device:\\+tbxi
>>
>> Which means the files which +tbxi attribute in the blessed directory.
>>
>> But efi only store the boot device (uuid), so it needs to use the
>> blessed file to boot.
>>
>> So to distinguish these two situation, we can have too options for bless:
>>
>> bless [--bootinfo PATH_TO_BOOTX] [[--bootefi PATH_TO_BOOTEFI]
>>
>> --bootinfo set the blessed directory plus +tbxi, while --bootefi set
>> the blessed file, this way we could specify different boot files for
>> openfirmware and efi, something like this:
>>
>> bless --bootinfo /grub.elf --bootefi grub.efi
>>
>
> Wouldn't it be possible to do a check in bless that determines if the
> file is for openfirmware of efi?
>
Actually it's even easy. EFI files are exes (Mark Zbykowsky or some
fat binaries signatures) while OFW files are ELF AFAIR
> Thanks
>
> Michal
>
>
> _______________________________________________
> Grub-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/grub-devel
>



-- 
Regards
Vladimir 'phcoder' Serbinenko

Personal git repository: http://repo.or.cz/w/grub2/phcoder.git