Hello,
I'm still experimenting GRUB and netboot. At the moment, one cannot load a
nbi compliant image. When GRUB loads that kind of image (saying Linux kernel
image made via mknbi-linux), GRUB reports that the image of the kernel is
too big, because of the special format of the image. What do you think :
1) Is it necessary to add a simple check about the two words magic number
0x1B031336 just in order to display a warning about the nbi format (and
avoiding, even if the case is rare, the puzzling error :"image too big
etc...");
2) I have searched the archive and found some mails from Okuji speaking
about the implementation of a kind of `nbi' command, loading the image,
parsing the header (described in etherboot distribution, "spec.txt"),
relocating the image, etc... But as far as I know, there are several
informations taken by the etherboot bootloader used in order to give the
kernel all the informations gathered. So :
Is it better to add a `nbi' command loading an _etherboot
bootloader_ (kind of chainloading),
or in fact a `nbi' command loading the image (results will not be
the same).
If it is the former, we will be between chainloading and `dynamic loading'
(kinda exec in fact for lowlevel executable).
Thank you for the advice,
--
Thierry LARONDE, Centre de Ressources Informatiques, Archamps - France
http://www.cri74.org
PingOO, serveur de com sur distribution GNU/Linux: http://www.pingoo.org
_______________________________________________
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub
