Re: Booting a modular kernel through a multiple streams file

[ebiederm@xmission.com (Eric W. Biederman)]

"Grover, Andrew" <andrew.grover@intel.com> writes:

> > From: ebiederm@xmission.com [mailto:ebiederm@xmission.com]
> > > Basically what Grub does is loads the kernel modules from disk
> > > into memory, and 'tells' the kernel the memory location to load
> > > them from, very similar to how an initrd file is loaded. The problem
> > > is Linux, is not MBS compilant and doesn't know to look for and load
> > > the modules. 
> > 
> > So tell me how you make an MBS compliant alpha kernel again?
> 
> 1) Someone writes a MBS spec chapter for Alpha

Nope it isn't that simple.  Multiboot doesn't extend gracefully at all,
not to multiple architectures, not to new parameters, not to multiple
vendors.   If you do extend it you get a real mess.

Which is why it is not good to adopt.  

> 2) Someone implements it.
> 
> Any volunteers? (Eric? ;-))

I've looked and I'm not going there.  Multiboot is just plain nasty,
and quite poorly specified as well.

I'll do something better but not that.  In fact I have already started...

> It's all about scratching an itch, right? Things don't become cross-platform
> by themselves. Linux started out 386-only, after all.

GRUB allows some very neat things and it allows for it with the
multiboot stuff.  And everyone seems to assume that because what you
can do with GRUB is good, multiboot must be good as well.  But have
you ever wondered why no other bootloader implementor was interested?

Eric