> > Anything that reduces dependencies on the BIOS is good. I'd use this
> > feature if it was available.
>
> But 'downloading' (actually uploading) software and writing it to flash
> for a re-boot is a trivial user-mode task. The actual boot from such a
> virtual disk takes 4 seconds on a real system (AMD SC520) processor in
> an embedded system. You don't need any special kernel hooks.
The flashing can be trivial, but downloading and verification of the
software is not. One of the systems I was working on required synchronous
PPP protocol and HDLC drivers to load the kernel. The network was
untrusted, so checking the signature of the kernel was a very good idea.
None of that functionality was required for normal operation. In fact, it
was preferred to disable any network protocols on the working nodes.
By the way, kexec makes it possible to avoid any write operations. The
bootstrap kernel can be in the true ROM (not PROM), the secondary kernel
can be loaded into the RAM.
Finally, I'm subscribed to the GNU GRUB mailing list, and it's quite
common to see people trying to boot their systems over 802.11 or something
like that, not to mention problems with large hard drives and USB
keyboards. kexec makes it possible to implement a bootloader with full
BIOS-independent support for USB keyboards and drives, IDE, SCSI and
everything else, even fancy animated logos on the framebuffer.
-- Regards, Pavel Roskin- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Oct 23 2002 - 22:01:05 EST