[ipxe-devel] unable to chain to a script

[Duane Voth]

Ah, ok, my source has been saying http://ipxe.org/2e008001 - the text on the
real error page is quite helpful - yes I was missing the she-bang line.  The
fetched script now registers as a script.

What was surprising tho is that all fetches in the fetched script are
relative to base directory of the script!  Is this the expected behavior?

Ex:

----- script 1 (embedded in ipxe)
#!ipxe
dhcp net0
route
imgfetch ipxe.cfg/boot1.ipxe
imgload boot1.ipxe
imgexec boot1.ipxe

----- script 2 (boot1.ipxe)
#!ipxe
imgfetch shellx64.efi

The tftp server (with verbose msgs) shows that the imgfetch in boot1.ipxe
asks for "ipxe.cfg/shellx64.efi".


Duane


On Wed, Dec 8, 2010 at 6:04 AM, Michael Brown <mbrown at fensystems.co.uk>wrote:

> On Wednesday 08 Dec 2010 00:05:06 Shao Miller wrote:
> > On 12/7/2010 18:31, Duane Voth wrote:
> > > I've been trying to run a remote script from ipxe (snponly version)
> > > but imgload complains with a 2e008001
> >
> > If you use a recent version of iPXE, you might notice that those error
> > codes are given as URIs.
> >
> >    http://ipxe.org/err/2e008001
> >
> > "Exec format error"
> >
> > Do you perhaps have "#!gpxe" in the script's she-bang, rather than
> > "#!ipxe" ?
>
> "#!gpxe" should also be recognised; gPXE scripts are currently a subset of
> iPXE scripts (with the single exception of the command "dhcp any" in gPXE,
> which is just "dhcp" in iPXE, for consistency with "ifopen" et al).
>
> It does sound as though the shebang line is not being recognised.  Could
> you
> possibly attach a copy of your script?
>
> Michael
> _______________________________________________
> ipxe-devel mailing list
> ipxe-devel at lists.ipxe.org
> https://lists.ipxe.org/mailman/listinfo/ipxe-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20101208/bd43f822/attachment.htm>