From: Jan Fricke <[EMAIL PROTECTED]>
Subject: BeOS loader
Date: Mon, 04 Sep 2000 12:51:42 +0200
> 1. In "grub" (i.e. the command line tool) the BeOS kernel will be loaded
> and the right size is indicated. But starting with "stage2" (i.e. real
> boot) and typing "kernel = /boot/kernel/Zbeos" the loading is aborted
> with an error message (sorry, I forgot the exact phrase) and typing it
> once again the computer makes immediately a hard reset.
That's probably because you load the kernel to 0x10100 while running
GRUB. This erases the code used by GRUB itself, so you shouldn't load
the kernel to the location directly. See the function `linux_boot' in
asm.S, to learn how to load a kernel below 0x100000 safely.
> 2. I don't know how to identify ("signature") a BeOS kernel. I didn't
> find any kind of appropriate data in the header -- it all seems to be
> code, except the loading message which I used to identify the kernel,
> but this can change.
Then, you should contact BeOS developers to add a signature so that
GRUB can recognize a BeOS kernel permanently. Another way is to use
the option `--type=' for the command `kernel', but this is
deprecated.
BTW, Gordon, what do you think about BeOS support? Obviously, BeOS
is proprietary software, so I'm not sure if we should accept patches
for such an OS. I myself have no objection to adding the support, as
this enables them to replace the proprietary boot loader with the free
boot loader (i.e. GNU GRUB), so we can give them more opportunity to
broaden the idea of free software.
Regards,
Okuji
