From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Barry Jackson <zen25000@zen.co.uk>
Cc: grub-devel@gnu.org
Subject: Re: grub-lnstall option (UEFI) for chainloading
Date: Sun, 29 Mar 2015 16:12:24 +0300 [thread overview]
Message-ID: <20150329161224.5192abb7@opensuse.site> (raw)
In-Reply-To: <5517EBD8.8070901@zen.co.uk>
В Sun, 29 Mar 2015 13:11:04 +0100
Barry Jackson <zen25000@zen.co.uk> пишет:
> Hello,
> Currently when installing grub2 on UEFI, the running system's grub2
> writes an entry to the ESP making it the controlling grub.
>
> Can an option to grub2-install be added that installs only to
> /boot/grub2 and creates core.efi, but does *not* write into the ESP?
>
> This would provide similar functionality to the --no-bootsector option
> used in PC-BIOS systems for using a Master grub partition that
> chainloads into multiple operating systems.
Yes, for a long time I cherish idea of "only update /boot/grub and
create core.img" option. May be something like generic
--no-platform-setup
that will simply exit after image is created. --no-nvram is too
specific name to roll this into it. We can then deprecate
--no-bootsector and --no-nvram (actually as --no-bootsector is new just
drop it).
Vladimir, will you agree to a patch?
next prev parent reply other threads:[~2015-03-29 13:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-29 12:11 grub-lnstall option (UEFI) for chainloading Barry Jackson
2015-03-29 13:12 ` Andrei Borzenkov [this message]
2015-03-30 9:32 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-03-30 9:58 ` Andrei Borzenkov
2015-06-05 13:56 ` Barry Jackson
2015-06-06 8:38 ` Andrei Borzenkov
2015-09-07 21:39 ` Barry Jackson
2015-10-12 9:31 ` Andrei Borzenkov
2015-10-12 16:39 ` Daniel Kiper
2015-10-12 20:08 ` Andrei Borzenkov
2015-10-12 20:59 ` Daniel Kiper
2016-06-06 11:20 ` Barry Jackson
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=20150329161224.5192abb7@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=zen25000@zen.co.uk \
/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.