Re: multiboot2: remove "a.out kludge" requirement

[Andrei E. Warkentin]

No, I think Okuji mentioned that he didn't want to omit the Multiboot header out of the possibility of not registering the Multiboot header's presence if it is past the 8K mark (i.e. corrupt multiboot kernel).

With a custom e_type you could be sure it's really a Multiboot kernel or not... and not ever be concerned with corrupt files with the header past 8K. 

Andrei Evgenievich Warkentin

address@hidden

Cell: (+1) (847) 321-15-55

On 17.11.2006, at 16:01, Hollis Blanchard wrote:

On Fri, 2006-11-17 at 15:27 -0600, Andrei E. Warkentin wrote:

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. 

Why would we need a custom e_type? We know how to load ELF; we can

already omit the multiboot header.

Are you worried about a user accidentally running "multiboot /bin/ls"?

I'm 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. 

How would it simplify the code?

(Modules are ET_REL, for the record.)

-Hollis

_______________________________________________

Grub-devel mailing list

address@hidden

http://lists.gnu.org/mailman/listinfo/grub-devel