From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: my plan for Multiboot 2
Date: Wed, 9 Dec 2009 23:03:51 +0100 [thread overview]
Message-ID: <20091209220351.GJ7093@thorin> (raw)
In-Reply-To: <4B201BC7.2050703@gmail.com>
On Wed, Dec 09, 2009 at 10:51:03PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> Robert Millan wrote:
> > Hi,
> >
> > We have an obvious problem with the Multiboot 2 loader: It's in
> > severe bitrot. Nobody complains because nobody uses it, which is
> > understandable given that nobody programs for MB2, because it's not
> > ready (both in spec and in implementation), and we don't improve it
> > because nobody complains, etc. You get the point :-)
> >
> > I think the approach that was taken has proven wrong. It might have
> > worked with more manpower, but our time resources are scarce and we have
> > other priorities. In my opinion, as things stand now it is best if
> > Multiboot 2 is developed by piggybacking on Multiboot 1 rather than as an
> > isolated effort. This idea is twofold: both in spec and in implementation.
> >
> >
> Do you plan on removing multiboot2 loader from grub2 and marking
> multiboot2 draft as abandonded?
I don't know. Do you think this would be necessary? I was thinking we could
gradually replace it in parallel, but I'm open to ideas/suggestions.
> I think cpu-independency should come after possible incompatible changes
> since if we bring bad but compatible decision to non-x86 then it will be
> difficult to eradicate.
I don't understand very well; could you give an example of problematic
situation?
--
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."
next prev parent reply other threads:[~2009-12-09 22:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 15:08 my plan for Multiboot 2 Robert Millan
2009-12-07 16:53 ` Samuel Thibault
2009-12-09 21:50 ` Robert Millan
2009-12-09 21:51 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-09 22:03 ` Robert Millan [this message]
2009-12-09 22:17 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-10 1:01 ` Robert Millan
2009-12-10 7:06 ` BVK Chaitanya
2009-12-13 8:13 ` Bogdan
2009-12-13 22:16 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-24 21:07 ` Robert Millan
2009-12-24 21:11 ` Robert Millan
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=20091209220351.GJ7093@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.