All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] New object format for grub2
Date: Fri, 10 Jul 2009 19:27:27 +0200	[thread overview]
Message-ID: <20090710172727.GE17114@thorin> (raw)
In-Reply-To: <87ws6jntc3.fsf@xs4all.nl>

On Wed, Jul 08, 2009 at 04:27:08PM +0200, Marco Gerards wrote:
> Hi,
> 
> Bean <bean123ch@gmail.com> writes:
> 
> > Why another format ? Here are some reason:
> >
> > The current object format is ELF. Most unix based os use ELF as native
> > object format, but there are minor difference, and gcc may add extra
> > segment which is of no use for grub. Mingw/cygwin uses PE, and we need
> > to convert it to ELF. Platform like OSX also requires special
> > treatment. All these make the build system complicated, so we might
> > just use an unified format specific to grub.
> >
> > The ELF format is designed to be compatible with many system, it's
> > neither compact nor easy to parse. If we invent a new format, we
> > should make it simple.
> 
> There is another problem with this: the maintainance burden.  People
> know ELF, we have ELF and people will know ELF in the future.
> Furthermore, as far as I am concerned, GNU/Linux is our main
> platform.  I do not mind supporting windows or so and we can support
> it in a sane way, but changing our binary formats for it is one step
> too far for me...

Hi,

Even if changing our binary format were deemed a good idea, I think this
is very bad timing for changing GRUB's core in such significant ways.

Remember that the majority of GRUB users are still running GRUB Legacy,
and we've just got started in migrating them.  Ubuntu has committed to
GRUB 2, and IMO we should try to give them a stable codebase for their
release.

This sort of changes tends to cause regressions.  Notice the hiddenmenu
one, introduced with the script engine split, which is still unsolved.
Hiddenmenu is what Ubuntu is currently using with GRUB Legacy.  It's
important that we can provide them with something equivalent.

-- 
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."



      parent reply	other threads:[~2009-07-10 17:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 11:31 [RFC] New object format for grub2 Bean
2009-07-08 14:27 ` Marco Gerards
2009-07-08 15:37   ` Bean
2009-07-08 18:51   ` Pavel Roskin
2009-07-08 22:57     ` Vladimir 'phcoder' Serbinenko
2009-07-08 23:21       ` Pavel Roskin
2009-07-10 17:33       ` Robert Millan
2009-07-10 17:27   ` 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=20090710172727.GE17114@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.