How about having a custom e_type for ELF images booted by GRUB?
Something in the range between ET_LOOS and ET_HIOS (the OS specific
types). This way one could avoid the Multiboot header in ELF, as the
file would itself would identify self as GRUB-bootable or not.
Also...
I am not familiar with the module architecture in GRUB2 (whether mods
are ET_REL or ET_DYN), but having a custom type for those would sure
simplify those code paths too.
Andrei Evgenievich Warkentin
[EMAIL PROTECTED]
Cell: (+1) (847) 321-15-55
On 17.11.2006, at 15:10, Hollis Blanchard wrote:
One requirement listed for multiboot2 was that ELF headers should be
ignored, because NetBSD was setting their ELF addresses incorrectly.
This has now been fixed (see
http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=32865), so
I've
removed that requirement.
ELF headers tell you where to load an executable far better than the
kludge, so it really doesn't make sense to ignore ELF.
-Hollis
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
