Re: gPXE scripts and boot module order

Have you tried fetching modules in the reverse order?

Here is a theory:

When gPXE downloads an image, memory is handed out from the top of
memory towards lower addresses.  The first image you download will
have a higher memory address than the second image you download.
(Details: core/downloader.c uses urealloc() to reserve memory for the
image being downloaded, arch/i386/interface/pcbios/memtop_umalloc.c
implements the umalloc() heap by growing it downwards.)

The multiboot code in gPXE will sort modules in ascending memory order
for OS compatibility reasons, therefore the last module you downloaded
is first in the list.  (Details: You will see a comment in
arch/i386/image/multiboot.c that says:
/* At least some OSes expect the multiboot modules to
 * be in ascending order, so we have to support it.
 */)

Hope this helps,
Stefan

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july