From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] multiboot2 loader
Date: Tue, 28 Nov 2006 12:25:49 +0100 [thread overview]
Message-ID: <200611281225.49710.okuji@enbug.org> (raw)
In-Reply-To: <20061128105953.GB13402@neonescio.viaisn.org>
On Tuesday 28 November 2006 11:59, Jeroen Dekkers wrote:
> On Tue, Nov 28, 2006 at 08:08:46AM +0100, Yoshinori K. Okuji wrote:
> > On Sunday 26 November 2006 11:18, Tomáš Ebenlendr wrote:
> > > What about having
> > > "Multiboot's" header as a part of "Multiboot project".
> >
> > Multiboot Specification is not a part of GRUB in any sense. It is
> > discussed in this list, only because that is the most realistic at the
> > moment, as all Multiboot developers are GRUB developers, too, AFAIK.
>
> Not part of GRUB in any sense?
No. It is explicitly written that this specification is to define a neutral
protocol between a boot loader and an operating system.
> It was developed by GRUB developers,
> has always been living in the GRUB repository, the official GRUB
> tarball includes it and AFAIK GRUB is the only bootloader to implement
> it.
I know at least one more project which implements Multiboot: Etherboot. The
support is partial, but it still supports Multiboot.
I talked about excluding the Multiboot Specification from GRUB with RMS a long
time ago, because it was not really a part of GRUB, and it looked like a part
of it, although it should be regarded as a generic specification, only
because it was bundled with GRUB. And, he said that it was more convenient
for people who would like to utilize GRUB to include the spec, and the spec
was small enough to distribute with GRUB. His argument sounded good, so I
decided to keep it.
But now it might be better to change my mind, since even _you_ misunderstand
it. If you don't get it, how many people would understand?
> Saying that multiboot isn't part of GRUB doesn't really make any
> sense to me. It could as well have been named "GRUB boot protocol" and
> nobody would consider that strange.
Don't generalize your idea without asking. The spec is not limited to GRUB,
and GRUB supports more protocols.
Okuji
next prev parent reply other threads:[~2006-11-28 11:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 1:16 [RFC] multiboot2 loader Hollis Blanchard
2006-11-15 20:33 ` Yoshinori K. Okuji
2006-11-15 21:10 ` Hollis Blanchard
2006-11-15 22:15 ` Yoshinori K. Okuji
2006-11-15 22:48 ` Hollis Blanchard
2006-11-25 2:56 ` Yoshinori K. Okuji
2006-11-26 10:18 ` Tomáš Ebenlendr
2006-11-26 16:35 ` Hollis Blanchard
2006-11-28 7:08 ` Yoshinori K. Okuji
2006-11-28 10:59 ` Jeroen Dekkers
2006-11-28 11:25 ` Yoshinori K. Okuji [this message]
2006-11-29 21:56 ` Jeroen Dekkers
2006-11-26 22:50 ` Jeroen Dekkers
2006-11-28 7:11 ` Yoshinori K. Okuji
2006-11-28 10:59 ` Jeroen Dekkers
2006-11-28 11:14 ` Yoshinori K. Okuji
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=200611281225.49710.okuji@enbug.org \
--to=okuji@enbug.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.