From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] New object format for grub2
Date: Wed, 08 Jul 2009 14:51:10 -0400 [thread overview]
Message-ID: <1247079070.26368.25.camel@mj> (raw)
In-Reply-To: <87ws6jntc3.fsf@xs4all.nl>
Hello, Marco!
On Wed, 2009-07-08 at 16:27 +0200, Marco Gerards wrote:
> 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...
There is actually a maintenance burden that is caused by the need to
support the ELF format. We need to strip some sections from the modules
for GRUB to process them correctly.
Support for "secondary" platforms means that the build system should
recognize of compile tools to convert their native formats to ELF. It's
more complex than having one converter for all platforms that is
completely under our control.
In addition to the problem on the core.img size, we have a problem of
the size of all the core plus modules. GRUB already barely fits the
boot partitions on PowerPC, and it won't fit if yaboot is to be
preserved. Soon it will push the limits of a 1.44Mb floppy (without any
kernels, mind you). And then there is an issue with writing GRUB on a
ROM.
I'm not exactly enthusiastic about another major change when we need
stabilization, but the maintenance argument really doesn't apply here.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-07-08 18:51 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 [this message]
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=1247079070.26368.25.camel@mj \
--to=proski@gnu.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.