From: Pavel Roskin <[EMAIL PROTECTED]>
Subject: GRUB executables
Date: Fri, 22 Oct 1999 19:53:10 +0400 (EEST)
> One of them would be generated by a modified isapnp from isapnp.conf
> I don't want to embed a bison parser into GRUB. It is much easier to
> generate i386 code that just writes to the ports.
I agree.
> Another executable could load Russian (or Japanese?) font.
> It is necessary because 99.9 % video cards sold in Russia don't have
> a Russian font in BIOS and the remaining 0.01% use CP-866 that is
> incompatible with Koi8-r used on Linux and *BSD.
Probably we should discuss how to internationalize GRUB. I talked
with Erich about it a bit, but more discussion is definitely
necessary. But I think it will need to rewrite much of the code, so
the actual implementation should be done after 0.6.
> By the way, can a Multiboot kernel just "return" to the bootloader?
> This would be the simplest solution.
I think dynamic loading would be the best solution. I and Gordon are
planning to break the Stage 2 into multiple components and strip the
user interface from the core component. So I called the core "GRUB
kernel" and the rest "GRUB user". At the time, I proposed that a GRUB
user should be just a Multiboot kernel, but now I propose that a GRUB
user should be a dynamic library object, because a dynamic object can
be located at arbitrary memory space while a static object must be
located at certain memory space. This funtionality will be necessary
if we have many, many modules.
For now, however, I'm planning to implement the netboot module as if
it is just a kernel, just because this is easy.
----------------------------------------------------------------------
OKUJI Yoshinori <[EMAIL PROTECTED]> ^o-o^
http://duff.kuicr.kyoto-u.ac.jp/~okuji (in English) m /
