From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Michael Chang <mchang@suse.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [RFC] grub-install: allow none or multiple install devices on PC BIOS
Date: Tue, 12 May 2015 14:57:00 +0300 [thread overview]
Message-ID: <20150512145700.195e76a7@opensuse.site> (raw)
In-Reply-To: <20150512105222.GA7529@linux-dsax.tai.apac.novell.com>
В 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.
> > 2. Redundant installation on multi-device filesystem, RAID or similar.
> > This allows both optimizing image w.r.t. to using --prefix vs. load.cfg
> > as well as creating image just once.
>
> I can only tell it to solve the problem of time wasting in copying
> modules and images creation due to multiple invocation of grub-install
> for doing redundency install. Beside that, do you foresee any other
> improvement it can provide?
>
You answered it yourself below. That is why I think it is useful mostly
for PC BIOS that is unique with embedding problem.
> >
> > Patch allows transparently use none or multiple installation devices,
> > similar to
> >
> > grub_devices="/dev/sda /dev/sda1 /dev/sdb"
>
> It also looks to me that this patch can solve the problem of multiple
> device install with blocklists. Think about the user installs to mbr
> (sda) and partition (sda1) because he someshow wants the paritition to
> be chainload-able for resuce or for any of his own interests.
>
> If the user occasionally do.
>
> grub-install /dev/sda1 grub-install /dev/sda
>
> The chainload will fail for sda1 since later install to mbr replaces the
> core.img.
>
Exactly. This was common problem for openSUSE users as at least in
earlier versions installer defaulted to multiple bootloader locations
and only some of them allowed embedding.
> You patch can avoid such pit-fall by doing it once.
>
> > grub-install $grub_devices
>
> What if one of the device failed, should it continue installing the rest
> or abort immediately ?
>
It will abort, unfortunately. Changing it is really intrusive as it
may happen deep in call chain which simply does grub_util_error(). It
is something that may be considered for the future. BTW as far as I can
tell pbl aborts installation if any of grub-install invocation failed.
next prev parent reply other threads:[~2015-05-12 11:57 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 [this message]
2015-05-12 14:57 ` Michael Chang
2015-05-12 15:22 ` Michael Chang
2016-02-13 7:29 ` Andrei Borzenkov
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=20150512145700.195e76a7@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=mchang@suse.com \
/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.