Ben,<br><br>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.<br><br>Linky: <a href="http://markmail.org/message/7sfph36gffd2haww">http://markmail.org/message/7sfph36gffd2haww</a><br>
<br>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.<br>
<br>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.<br><br>
If you have more questions about the patch, Shao may be best suited to answer them.<br><br>Enjoy,<br>Andrew Bobulsky <br><br><div class="gmail_quote">On Wed, Apr 14, 2010 at 9:16 PM, Ben Derstine <span dir="ltr"><<a href="mailto:BLD17@sa.psu.edu">BLD17@sa.psu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hi Shao,<br>
<br>
The cmdline patch would be very helpful. How do I build gpxe with it?<br>
<font color="#888888"><br>
<br>
Ben<br>
</font><div><div></div><div class="h5"><br>
-----Original Message-----<br>
From: Shao Miller [mailto:<a href="mailto:Shao.Miller@yrdsb.edu.on.ca">Shao.Miller@yrdsb.edu.on.ca</a>]<br>
Sent: Wednesday, April 14, 2010 3:36 PM<br>
To: Ben Derstine<br>
Cc: <a href="mailto:gpxe@etherboot.org">gpxe@etherboot.org</a><br>
Subject: Re: [gPXE] SUSPECT: Re: Local menu system for gpxe<br>
<br>
Good day Ben,<br>
<br>
In regards to a means to configure gPXE's IP parameters before booting:<br>
<br>
Embed the following gPXE script (~/myscript.gpxe):<br>
<br>
#!gpxe<br>
set ip 192.168.0.3<br>
set netmask 255.255.255.0<br>
set gateway 192.168.0.1<br>
set dns 10.113.114.8<br>
config<br>
set 209:string pxelinux.cfg/default<br>
set 210:string <a href="http://webserver/" target="_blank">http://webserver/</a><br>
chain ${210:string}pxelinux.0<br>
<br>
Embed the script into your gPXE build like this:<br>
<br>
~$ cd gpxe/src<br>
~/gpxe/src$ make EMBEDDED_IMAGE=~/myscript.gpxe bin/gpxe.usb<br>
...<br>
~/gpxe/src$ dd if=bin/gpxe.usb of=/dev/sdb<br>
<br>
where /dev/sdb would be a USB stick whose entire contents would be<br>
erased.<br>
<br>
The above is a sample for how you can pre-populate a few IP parameters,<br>
then use gPXE's 'config' command to hack them just before trying to boot<br>
<br>
to a PXELINUX that will boot from some webserver. I'll be you could<br>
adapt this to your needs.<br>
<br>
Alternatively, there is a patch for gPXE that allows you to pass<br>
commands to gPXE from another boot-loader, such as Syslinux. You might<br>
find this convenient, so you could have something like:<br>
<br>
LABEL site_a<br>
KERNEL gpxe.lkrn<br>
APPEND set ip=192.168.0.3; set gateway 192.168.0.1<br>
LABEL site_b<br>
KERNEL gpxe.lkrn<br>
APPEND set ip=192.168.1.3; set gateway 192.168.1.1<br>
<br>
where you'd then only need a single gpxe.lkrn who could have the<br>
following embedded script:<br>
<br>
#!gpxe<br>
set netmask 255.255.255.0<br>
set dns 10.113.114.8<br>
config<br>
set 209:string pxelinux.cfg/default<br>
set 210:string <a href="http://webserver/" target="_blank">http://webserver/</a><br>
chain ${210:string}pxelinux.0<br>
<br>
The patch is called something like the "gPXE lkrn initrd cmdline patch."<br>
<br>
- Shao Miller<br>
_______________________________________________<br>
gPXE mailing list<br>
<a href="mailto:gPXE@etherboot.org">gPXE@etherboot.org</a><br>
<a href="http://etherboot.org/mailman/listinfo/gpxe" target="_blank">http://etherboot.org/mailman/listinfo/gpxe</a><br>
</div></div></blockquote></div><br>