All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Suchanek <hramrach@centrum.cz>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] bless command
Date: Sat, 29 Aug 2009 10:43:45 +0200	[thread overview]
Message-ID: <a5d587fb0908290143p73f00a15ja765add17598d18d@mail.gmail.com> (raw)
In-Reply-To: <ca0f59980908290110y3213bf8q94abc19ec2f5d005@mail.gmail.com>

2009/8/29 Bean <bean123ch@gmail.com>:
> On Sat, Aug 29, 2009 at 3:58 PM, Michal Suchanek<hramrach@centrum.cz> wrote:
>> 2009/8/29 Bean <bean123ch@gmail.com>:
>>> On Sat, Aug 29, 2009 at 2:27 PM, Vladimir 'phcoder'
>>> Serbinenko<phcoder@gmail.com> 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?
>
> Hi,
>
> I think it would be better to specify the type explicitly, as there
> are multiple formats supports by both platform. OpenFirmware support
> bootinfo, xcoff and elf, while efi support i386-efi, x86_64-efi and
> fat binary.
>

They are multiple but different. I guess automatic detection would be
nice to have but writing detection for multiple formats might take
some time so it would be better to get a bless command without
detection initially and possibly add detection later.

Thanks

Michal



  reply	other threads:[~2009-08-29  8:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-18 18:59 [PATCH] bless command Vladimir Serbinenko
2009-04-18 19:00 ` Vladimir Serbinenko
2009-04-18 19:22 ` Isaac Dupree
2009-04-19  4:51 ` Peter Cros
2009-04-19 10:50   ` Vladimir Serbinenko
2009-04-19 11:25     ` Drew Rosen
2009-04-19 13:26     ` Peter Cros
2009-04-19 14:14       ` Vladimir Serbinenko
2009-04-19 15:30         ` Peter Cros
2009-04-19 20:05           ` Vladimir Serbinenko
2009-04-20  9:17             ` Peter Cros
2009-04-20 11:52               ` Vladimir Serbinenko
2009-04-21  2:28                 ` Peter Cros
2009-08-28 22:59         ` Michal Suchanek
2009-08-29  3:48           ` Bean
2009-08-29  6:27             ` Vladimir 'phcoder' Serbinenko
2009-08-29  7:53               ` Bean
2009-08-29  7:58                 ` Michal Suchanek
2009-08-29  8:07                   ` Vladimir 'phcoder' Serbinenko
2009-08-29  8:10                   ` Bean
2009-08-29  8:43                     ` Michal Suchanek [this message]
2009-08-29  8:06                 ` Vladimir 'phcoder' Serbinenko
2009-06-19  6:08 ` Peter Cros
2009-06-19 11:53   ` Vladimir 'phcoder' Serbinenko
2009-06-19 16:15     ` Pavel Roskin
2009-06-19 16:24       ` Vladimir 'phcoder' Serbinenko
2009-06-21 11:05     ` Robert Millan
2009-08-28 15:19       ` Vladimir 'phcoder' Serbinenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a5d587fb0908290143p73f00a15ja765add17598d18d@mail.gmail.com \
    --to=hramrach@centrum.cz \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.