From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Multiboot2 header
Date: Fri, 7 Nov 2008 20:53:57 +0100 [thread overview]
Message-ID: <20081107195357.GG8625@thorin> (raw)
In-Reply-To: <200811061823.15421.okuji@enbug.org>
On Thu, Nov 06, 2008 at 06:23:15PM +0100, Yoshinori K. Okuji wrote:
> On Tuesday 04 November 2008 21:36:27 Robert Millan wrote:
> > The Multiboot2 draft says a Multiboot2 header must be included in the OS
> > image. However, our code assumes (in code itself and in comments) that for
> > MB2 this is optional.
> >
> > As a consequence, if you feed GRUB's multiboot loader any ELF, it will
> > attempt to load it. I think this is very confusing for those developing
> > a Multiboot _1_ OS. If they happen to make a mistake and put the MB1
> > header too high or unaligned, GRUB won't tell them about it but instead
> > fail in a very confusing way.
> >
> > So I assume (I'd like to!) that the correct one is the draft, and it's the
> > code that should be changed to reject executables that don't have either
> > MB1 or MB2 headers?
>
> Yes. The code is wrong.
Okay. The fix was fairly simple, I just checked it in.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
prev parent reply other threads:[~2008-11-07 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 20:36 Multiboot2 header Robert Millan
2008-11-05 17:40 ` Tomáš Ebenlendr
2008-11-06 17:23 ` Yoshinori K. Okuji
2008-11-07 19:53 ` Robert Millan [this message]
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=20081107195357.GG8625@thorin \
--to=rmh@aybabtu.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.