From: Robert Millan <rmh@aybabtu.com>
To: e_mc_h2@web.de
Cc: "Neal H. Walfield" <neal@gnu.org>, grub-devel@gnu.org
Subject: Re: bugs in loader/i386/pc/multiboot.c
Date: Sun, 22 Feb 2009 01:52:11 +0100 [thread overview]
Message-ID: <20090222005211.GA29483@thorin> (raw)
Hi,
The problem with elf64 in our multiboot loader is that it duplicates a lot
of code from elf32 and this eventually leads to bitrot.
In fact, grub_multiboot_load_elf32 and grub_multiboot_load_elf64 are supposed
to be almost identical, and only differ in s/32/64/ references.
It'd be fairly simple to resincronize them, but I'd really like to find a
way to prevent this from happening again.
Does someone have any idea on what would be a good approach?
--
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 reply other threads:[~2009-02-22 0:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-22 0:52 Robert Millan [this message]
2009-02-22 9:27 ` bugs in loader/i386/pc/multiboot.c phcoder
2009-02-27 21:41 ` Robert Millan
2009-02-27 22:01 ` Neal H. Walfield
2009-02-27 23:06 ` Robert Millan
2009-03-01 21:41 ` Neal H. Walfield
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=20090222005211.GA29483@thorin \
--to=rmh@aybabtu.com \
--cc=e_mc_h2@web.de \
--cc=grub-devel@gnu.org \
--cc=neal@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.