[gPXE] SUSPECT: Re: Local menu system for gpxe

[Andrew Bobulsky]

Ben,

I think Shao may have retired for the evening, but a quick google search
shows that he wrote the patch he's referring to and sent it to the gPXE dev
mailing list.

Linky: http://markmail.org/message/7sfph36gffd2haww

I don't know what the likelihood of this patch working on 1.0.0+, and I
don't see anything in the patch file indicating what version of gPXE it was
written against, but you may find something, or perhaps it'll work against
1.0.0+, but I simply don't know.

As to using the patch, I imagine you just throw it into your gpxe/src
directory and "patch -p 0 < filename.patch" but I could be wrong there
too... not much source manipulation experience on my end.

If you have more questions about the patch, Shao may be best suited to
answer them.

Enjoy,
Andrew Bobulsky

On Wed, Apr 14, 2010 at 9:16 PM, Ben Derstine <BLD17 at sa.psu.edu> wrote:

> Hi Shao,
>
> The cmdline patch would be very helpful.  How do I build gpxe with it?
>
>
> Ben
>
> -----Original Message-----
> From: Shao Miller [mailto:Shao.Miller at yrdsb.edu.on.ca]
> Sent: Wednesday, April 14, 2010 3:36 PM
> To: Ben Derstine
> Cc: gpxe at etherboot.org
> Subject: Re: [gPXE] SUSPECT: Re: Local menu system for gpxe
>
> Good day Ben,
>
> In regards to a means to configure gPXE's IP parameters before booting:
>
> Embed the following gPXE script (~/myscript.gpxe):
>
> #!gpxe
> set ip 192.168.0.3
> set netmask 255.255.255.0
> set gateway 192.168.0.1
> set dns 10.113.114.8
> config
> set 209:string pxelinux.cfg/default
> set 210:string http://webserver/
> chain ${210:string}pxelinux.0
>
> Embed the script into your gPXE build like this:
>
> ~$ cd gpxe/src
> ~/gpxe/src$ make EMBEDDED_IMAGE=~/myscript.gpxe bin/gpxe.usb
> ...
> ~/gpxe/src$ dd if=bin/gpxe.usb of=/dev/sdb
>
> where /dev/sdb would be a USB stick whose entire contents would be
> erased.
>
> The above is a sample for how you can pre-populate a few IP parameters,
> then use gPXE's 'config' command to hack them just before trying to boot
>
> to a PXELINUX that will boot from some webserver.  I'll be you could
> adapt this to your needs.
>
> Alternatively, there is a patch for gPXE that allows you to pass
> commands to gPXE from another boot-loader, such as Syslinux.  You might
> find this convenient, so you could have something like:
>
> LABEL site_a
>  KERNEL gpxe.lkrn
>  APPEND set ip=192.168.0.3; set gateway 192.168.0.1
> LABEL site_b
>  KERNEL gpxe.lkrn
>  APPEND set ip=192.168.1.3; set gateway 192.168.1.1
>
> where you'd then only need a single gpxe.lkrn who could have the
> following embedded script:
>
> #!gpxe
> set netmask 255.255.255.0
> set dns 10.113.114.8
> config
> set 209:string pxelinux.cfg/default
> set 210:string http://webserver/
> chain ${210:string}pxelinux.0
>
> The patch is called something like the "gPXE lkrn initrd cmdline patch."
>
> - Shao Miller
> _______________________________________________
> gPXE mailing list
> gPXE at etherboot.org
> http://etherboot.org/mailman/listinfo/gpxe
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://etherboot.org/pipermail/gpxe/attachments/20100414/2c2c1ab2/attachment.html