From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: workaround install boot on btrfs with windows partition scheme
Date: Mon, 3 Nov 2014 08:31:58 +0300 [thread overview]
Message-ID: <20141103083158.6cff503b@opensuse.site> (raw)
In-Reply-To: <DD4A730D-68A2-4CD3-A517-413C41223CDC@colorremedies.com>
В Sun, 2 Nov 2014 15:11:29 -0700
Chris Murphy <lists@colorremedies.com> пишет:
>
> On Nov 1, 2014, at 11:27 PM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
>
> > В Sat, 1 Nov 2014 14:35:57 -0600
> > Chris Murphy <lists@colorremedies.com> пишет:
> >>
> >> Why not have a dedicated partition with MBR type code for core.img, equivalent to BIOSBoot currently used on GPT? freedesktop.org has a proposal to use type code 0xEA for this purpose (in part). The boot.img code in the MBR can arbitrarily jump to any LBA, so 0xEA doesn't need to be a primary partition does it?
> >>
> >
> > It is rarely needed in simple cases; in complicated cases (btrfs or
> > LVM) we already have space dedicated for core.img. It seems more
> > logical to use this space.
>
> Well actually it isn't rare in simple cases. The most common case on Linux is booting from ext which grub won't embed to either without --force.xz_dec_lzma2
We are discussing installation in MBR here, not in partition.
> So we have to have core.img embedded somewhere else. UEFI it's a fixed
location. BIOS+GPT it's a fixed location. Only on MBR is it in an
unreserved location or forcibly embedded - that's really where the
problem is. It seems a lot simpler to constrain the MBR options down
to only a reserved partition just like elsewhere where it's now much
simpler because it can only properly go in one location.
>
>
> > Also you still need to tell grub-setup to use this special partition at
> > which point why not extend it to support arbitrary location for
> > core.img? It could be made check partition type and not refuse to
> > install on raw partition for special 0xEA type then as a bonus.
>
> I never tell grub-setup to use BIOSboot partition type. It always just finds it automatically.
>
I do not really trust anyone respect partition types on MBR to be
honest. So I would rather avoid blindly overwriting anything without
explicit user's consent.
next prev parent reply other threads:[~2014-11-03 5:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 8:32 workaround install boot on btrfs with windows partition scheme Michael Chang
2014-10-30 12:42 ` Andrei Borzenkov
2014-11-02 1:34 ` Chris Murphy
2014-11-02 5:37 ` Andrei Borzenkov
2014-11-02 22:19 ` Chris Murphy
2014-11-03 5:36 ` Andrei Borzenkov
2014-11-03 19:36 ` Chris Murphy
2014-11-03 20:29 ` Andrei Borzenkov
2014-11-03 21:05 ` Chris Murphy
2014-11-04 5:50 ` Andrei Borzenkov
2014-11-04 6:46 ` Chris Murphy
2014-11-03 4:17 ` Michael Chang
2014-11-03 20:04 ` Chris Murphy
2014-11-04 4:50 ` Michael Chang
2014-11-04 18:21 ` Chris Murphy
2014-11-01 20:35 ` Chris Murphy
2014-11-02 5:27 ` Andrei Borzenkov
2014-11-02 22:11 ` Chris Murphy
2014-11-03 5:31 ` Andrei Borzenkov [this message]
2014-11-03 19:08 ` Chris Murphy
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=20141103083158.6cff503b@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=lists@colorremedies.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.