OKUJI Yoshinori <[EMAIL PROTECTED]> writes:
> > I have appended a patch that adds a new "modaddr" builtin command to
> > GRUB. This command specifies the load address for Multiboot modules.
> > It can only be used after a Multiboot kernel has been loaded.
>
> I think this command is dangerous for end-users, and that's a dirty
> solution.
I don't think that the command as such is bad. However, I agree that
the implementation should be improved: It should only allow increasing
the current load address to avoid overlaps with kernels and modules
loaded earlier.
> Is it better to put a header section in a module so that GRUB
> can load it in the suitable address transparently? I want to call the
> header "Multiboot module header", and the structure would be:
>
> struct mb_module_header
> {
> unsigned long magic; /* the magic number */
> unsigned long flags; /* the flags */
> unsigned long start_addr; /* the staring address to be loaded */
> unsigned long end_addr; /* the end address to be loaded */
> };
I don't think it is a good idea to invent yet another binary format.
Instead, we might consider adding a command that loads ELF binaries as
multiboot modules.
Michael
--
[EMAIL PROTECTED], [EMAIL PROTECTED]
http://www.sax.de/~hohmuth/
