forgive me to being insistent, i am new to all this stuff<br><br>can ipxe the ability to read and interpret a text config file during execution time ? .. this way you can, say, compile with<br><br>---------<br><br># make bin/undionly.kpxe EMBEDDED_IMAGE=conf_loader.ipxe<br>
ok<br><br># cat conf_loader.ipxe<br>#!ipxe<br>
include default.ipxe<br><br># ls /pxeboot<br>undionly.kpxe<br>default.ipxe<br>2nd_stage.ipxe<br><br># cat /pxeboot/default.ipxe<br>#!ipxe<br>dhcp<br>
chain <a href="http://server/fixed-boot-url" target="_blank">http://server/fixed-boot-url</a><br>include 2nd_stage.ipxe<br>more_comands<br>etc.<br><br>(booting)<br><br># tail -f /var/log/tftp.log<br>
001 sending file /pxeboot/undionly.kpxe to 192.168.1.2<br>
002 sending file /pxeboot/default.ipxe to 192.168.1.2<br>003 sending file /pxeboot/2nd_stage.ipxe to 192.168.1.2<br>
<br>(client screen)<br><br>pxe loader<br>requesting ip from dhcp<br>found, assigned ip 192.168.1.2<br>retrieving file undionly.kpxe ... ok<br>running<br>welcome to ipxe blah blah<br>requesting config file default.ipxe ... ok<br>
requesting config file 2nd_stage.ipxe ... ok<br>etc.<br><br>-------------------------<br><br>can ipxe the ability to handle variables names in real time ? ... this way you can do<br><br># cat myboot.ipxe<br>#!ipxe<br>
dhcp<br>
chain http://${TFTP_IP}/ipxeboot<br><br># make bin/undionly.kpxe EMBEDDED_IMAGE=myboot.ipxe<br><br>so this way you could distribute a pre-compiled image, and TFTP_IP can be replaced by actual ip used in boot time .. this way we can run an http server in same machine as tftp server and benefit with http features<br>
<br>-------------------<br><br>questions:<br><br>- what are http headers (or querystring) sended by ipxe? .. mac address?, client ip, ipxe version, machine achitecture? (i.e.: to handle with server scripting)<br>- what are response headears handled by ipxe? .. "301 location moved"? (i.e.: to do redirections, chainloads)<br>
<br>-------------------<br><br>i am trying to boot an iso image with pxe but is sooo damn slow .. i would like to do with pxe to load ipxe first, and then doing with http .. but i would like to ipxe become easier to use, fast, and flexible, avoiding the need to recompile with every change<br>
<br>please consider to implement a forum .. all we have always access to web, but not all have access to email all the time, is slower and less massive though.. web is more accessible and popular than irc, and if you are not online you can read messages later (or get alerted by email) .. there are plenty of oss forum engines, like smf and phpbb, or forum server hosts<br>
<br><br>thanks<br><br><br><br><div class="gmail_quote">On Wed, Mar 30, 2011 at 8:13 PM, Michael Brown <span dir="ltr"><<a href="mailto:mbrown@fensystems.co.uk">mbrown@fensystems.co.uk</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;">
<div class="im">On Wednesday 30 Mar 2011 23:16:34 AT - HE wrote:<br>
> i am trying to discover and use ipxe .. i think is a terrific piece of<br>
> software<br>
<br>
</div>Thank you!<br>
<div class="im"><br>
> however is a bit difficult to customize, not all can (or know) always<br>
> compile code<br>
><br>
> is there an option to "include" config files?<br>
<br>
</div>You can include an embedded script, which I think is what you want. There's<br>
some documentation about this at<br>
<br>
<a href="http://ipxe.org/scripting#embedded_scripts" target="_blank">http://ipxe.org/scripting#embedded_scripts</a><br>
<br>
At the moment, this still requires you to compile iPXE, but you don't have to<br>
modify any source code. All you need to do is create a custom script such as<br>
my_script.ipxe:<br>
<br>
#!ipxe<br>
dhcp<br>
chain <a href="http://server/fixed-boot-url" target="_blank">http://server/fixed-boot-url</a><br>
<br>
and then build iPXE using<br>
<br>
make bin/undionly.kpxe EMBEDDED_IMAGE=my_script.ipxe<br>
<br>
(assuming that undionly.kpxe is the type of iPXE binary that you want to use).<br>
<div class="im"><br>
> .. that way default binary package could have an integrated reference to<br>
> "include default.ipxe", which maybe can be loaded aside "boot.kpxe" binary<br>
> using the same protocol before run .. this could give us the freedom and<br>
> ease to write a "default.ipxe" config file according with our needs and<br>
> without needing of edit and recompile entire code<br>
<br>
</div>At some point soon(ish), there will be a web interface that allows you to<br>
build iPXE images without having to compile it yourself. At this point in<br>
time, you do need to compile.<br>
<div class="im"><br>
> can you install a forum? .. is a bit difficult to share ideas, get help and<br>
> communicate with you<br>
<br>
</div>You can use this mailing list, or if you want more interaction you can join<br>
the IRC channel (#ipxe on <a href="http://irc.freenode.net" target="_blank">irc.freenode.net</a>). There are usually around 30<br>
people in the IRC channel (including me), and many of us would be happy to<br>
help you there.<br>
<font color="#888888"><br>
Michael<br>
</font></blockquote></div><br>