All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [RFC] grub-install: allow none or multiple install devices on PC BIOS
Date: Sat, 13 Feb 2016 10:29:58 +0300	[thread overview]
Message-ID: <56BEDB76.1090301@gmail.com> (raw)
In-Reply-To: <20150512152206.GA10504@linux-dsax.tai.apac.novell.com>

12.05.2015 18:22, Michael Chang пишет:
> On Tue, May 12, 2015 at 02:57:00PM +0300, Andrei Borzenkov wrote:
>> В Tue, 12 May 2015 18:52:22 +0800
>> Michael Chang <mchang@suse.com> пишет:
>>
>>> On Fri, May 08, 2015 at 09:53:41PM +0300, Andrei Borzenkov wrote:
>>>> There are two main applications.
>>>>
>>>> 1. Omit install device to create generic image intended for chainloading
>>>> from other master loader. Such image can be put on any device (or file
>>>> system) and will still be able to find its $root. Currently even with
>>>> --no-bootsector grub-install optimizes image by skipping UUID search if
>>>> possible.
>>>>
>>
>> Actually I think it is useful for all platforms.
> 
> As it works across all platform, os-prober should consider chanloading
> core images if possible rather than digging into grub configs. Is there
> any plan for that ?
> 

At least on EFI it is not possible to chainload GRUB from /boot until it
supports multiboot; and even then it will be multiboot2, so it means
separate commands. We have enough issues with efi-specific linux loaders :(



  reply	other threads:[~2016-02-13  7:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 18:53 [RFC] grub-install: allow none or multiple install devices on PC BIOS Andrei Borzenkov
2015-05-12 10:52 ` Michael Chang
2015-05-12 11:57   ` Andrei Borzenkov
2015-05-12 14:57     ` Michael Chang
2015-05-12 15:22     ` Michael Chang
2016-02-13  7:29       ` Andrei Borzenkov [this message]
2016-02-16  4:11         ` Michael Chang
2016-02-16 18:11           ` Andrei Borzenkov
2016-02-12 18:41 ` Vladimir 'φ-coder/phcoder' Serbinenko
2016-02-13  7:27   ` Andrei Borzenkov

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=56BEDB76.1090301@gmail.com \
    --to=arvidjaar@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.