From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: Bryan Ford <baford@cs.utah.edu>, bug-grub@gnu.org
Subject: Re: Multiboot Specification
Date: Sun, 24 Feb 2008 18:52:10 +0100 [thread overview]
Message-ID: <20080224175210.GA8492@thorin> (raw)
In-Reply-To: <19f34abd0802240401m29b95768tb0d69b8f1af6a1f9@mail.gmail.com>
On Sun, Feb 24, 2008 at 01:01:00PM +0100, Vegard Nossum wrote:
> Hello,
>
> I have a question/comment regarding the Multiboot Specification. Since
> loaders need to read/load an object file anyway, wouldn't it be more
> appropriate to look for the multiboot header by looking up either a
> symbol name or a section name, rather than searching for a magic
> number within the first 8K bytes of the image?
>
> This shouldn't be very difficult to implement for loaders, it would
> make loading safer (more reliable), and it would remove an otherwise
> artificial limitation. (It wouldn't have to be a requirement, but it
> could be a supplement to the magic number solution.)
>
> How would I proceed to suggest this change? :-)
>
> Kind regards,
> Vegard Nossum
>
>
> PS: It wasn't entirely clear who is responsible for the specification.
> If I hit the wrong address, please disregard this message :-)
grub-devel the right place, but I don't know the answer. So just wait and be
patient :-)
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call… if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2008-02-24 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 12:01 Multiboot Specification Vegard Nossum
2008-02-24 17:52 ` Robert Millan [this message]
2008-02-26 22:31 ` Yoshinori K. Okuji
2008-02-27 7:29 ` Vegard Nossum
2008-02-27 7:35 ` Vegard Nossum
[not found] <200802271909.m1RJ9Rdc001108@shoebox.dholloway.com>
2008-02-28 10:21 ` David Holloway
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=20080224175210.GA8492@thorin \
--to=rmh@aybabtu.com \
--cc=baford@cs.utah.edu \
--cc=bug-grub@gnu.org \
--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.