All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] bless command
Date: Sat, 29 Aug 2009 10:06:19 +0200	[thread overview]
Message-ID: <d7ead6de0908290106t1c207b22ud85b4a0ba9bec9d6@mail.gmail.com> (raw)
In-Reply-To: <ca0f59980908290053v1f9ba93cjbfe779916ad35192@mail.gmail.com>

> 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
The --botinfo and --bootefi in this case are independent. I don't see
why it would be stuffed in the same command. What about:
blessefi - change blessed file
blessofw - change blessed directory +tbxi
blessdir - change blessed directory
>
> --
> Bean
>
> gitgrub home: http://github.com/grub/grub/
> my fork page: http://github.com/bean123/grub/
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>



-- 
Regards
Vladimir 'phcoder' Serbinenko

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



  parent reply	other threads:[~2009-08-29  8:06 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
2009-08-29  8:06                 ` Vladimir 'phcoder' Serbinenko [this message]
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=d7ead6de0908290106t1c207b22ud85b4a0ba9bec9d6@mail.gmail.com \
    --to=phcoder@gmail.com \
    --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.