That's already what initrd does. What would make this interesting --
and why, at least in my opinion, Multiboot is the wrong solution -- is
to make the bootloader smarter about what it loads. If the boot
loader can *probe* for the device- and filesystem drivers it needs and
thus dynamically compose the kernel in a dynamic manner, then it is
suddenly a win; not sooner. Multiboot doesn't do that, although it
might be possible to build on top of it to get there.
-hpa
-- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com> - 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/