From: Hollis Blanchard <hollis@penguinppc.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] multiboot2 loader
Date: Sun, 26 Nov 2006 10:35:56 -0600 [thread overview]
Message-ID: <1164558956.9086.3.camel@diesel> (raw)
In-Reply-To: <1399.84.242.81.204.1164536314.squirrel@drak.ucw.cz>
On Sun, 2006-11-26 at 11:18 +0100, Tomáš Ebenlendr wrote:
>
> >> There is plenty of precedent here. So I still see nothing wrong
> with
> >> putting a header file, which describes an interface, under a
> non-GPL
> >> license.
> >
> > Because GRUB is not a library. The spec is available independently,
> so
> > you can write your own header easily. Nothing prevents you from
> doing
> > this.
> >
> > Okuji
> >
>
> And should the multiboot header file be "Grub's"? What about having
> "Multiboot's" header as a part of "Multiboot project". Such project
> should
> contain only specification, and header file, that can be freely
> copied.
> The only thing that should be forbidden is that some third party will
> claim she owns the header. I think that GPL is too restrictive for
> this
> purpose. Such header file can be then added to grub as well as to
> BSD-licenced and other software.
Great point. A "multiboot" project could easily be created, and wouldn't
even need the approval of the GRUB project.
Beyond the specification and header file, it could also contain a "Hello
World" multiboot kernel.
-Hollis
next prev parent reply other threads:[~2006-11-26 16:36 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 [this message]
2006-11-28 7:08 ` Yoshinori K. Okuji
2006-11-28 10:59 ` Jeroen Dekkers
2006-11-28 11:25 ` Yoshinori K. Okuji
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=1164558956.9086.3.camel@diesel \
--to=hollis@penguinppc.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.