Re: Grokking miniroot.kmod etc.

[Hubert Feyrer <hubert%feyrer.de@localhost>]

Hi,

Am 17.11.2008 um Mo, 17. 11 2008, 14:34 schrieb Andrew Doran:
> We add the ramdisk image to miniroot.kmod as an ELF section:
>
> http://nxr.homeunix.org/source/xref/distrib/i386/kmod/Makefile#15
>
> When miniroot.kmod is first built from miniroot.c, it contains nothing
> other than the small code fragment in that file. It's useless until  
> the
> ELF object has had the disk image added.

OK


> >  * How to tell the bootloader to load the ramdisk after the kernel?
> >    My guess this is done via boot.cfg - is there an example?
>
> boot.cfg on the install CD:
>
> http://nxr.homeunix.org/source/xref/distrib/i386/cdroms/installcd/ 
> boot.cfg.in
>
> The 'load' commands can be given at any time. They are processed after
> the kernel has been loaded, but before the kernel has been started.

OK... I tried to build the ISO in there, but didn't really succeed.  
What target to I pass to make in .../distrib/i386/cdroms/installcd to  
get an ISO that uses boot.cfg and the module etc.? "prepare" and  
"iso_image" give me an ISO that uses an old-school embedded ramdisk.


> >    What is the /ramdisk.kmod mentioned in boot.cfg.4, is it the
> >    ramdiskbin.fs? Where exactly is this put?
>
> It should say miniroot.kmod, someone made a mistake.

Please check... I'm not sure what the exact point of mentioning this  
is, as it's not mentioned in the text at all. Maybe the whole process  
should be described somewhere?


 - Hubert