All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] New object format for grub2
Date: Wed, 08 Jul 2009 16:27:08 +0200	[thread overview]
Message-ID: <87ws6jntc3.fsf@xs4all.nl> (raw)
In-Reply-To: <ca0f59980907080431v15d9e136t3c8d82f9592f1b5b@mail.gmail.com> (bean123ch@gmail.com's message of "Wed, 8 Jul 2009 19:31:46 +0800")

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

--
Marco




  reply	other threads:[~2009-07-08 14: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 [this message]
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

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=87ws6jntc3.fsf@xs4all.nl \
    --to=mgerards@xs4all.nl \
    --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.