<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<tt>Tal Aloni wrote:</tt>
<blockquote type="cite" cite="mid:A4765EB4FA674E6881C318711A64777D@tal">
<style></style>
<div><tt><font size="2">Hi guys,</font></tt></div>
<div><tt><font size="2">I'm using gPXE for a year now and I'm loving
it, Thanks to all developers involved,</font></tt></div>
<div><tt><font size="2">one thing that I'm missing is a way to define
my own commands, </font><font size="2">that will execute gPXE commands
/ batch scripts.</font></tt></div>
</blockquote>
<tt><br>
You can embed multiple scripts by compiling like this:<br>
<br>
# cd gpxe/src/<br>
# make EMBEDDED_IMAGE=script1.gpxe,script2.gpxe,script3.gpxe
bin/gpxe.lkrn<br>
<br>
Where gpxe.lkrn is whatever build target you use. Then you can run
your scripts from the CLI like this:<br>
<br>
gPXE> chain script1.gpxe<br>
<br>
But perhaps you'd rather use aliases by using a script like this:<br>
<br>
#!gpxe<br>
set san1 sanboot iscsi:192.168.1.11<br>
set san2 sanboot iscsi:192.168.1.11::::win7<br>
echo Aliases have been set.<br>
<br>
gPXE> ${san1}<br>
<br>
or<br>
<br>
gPXE> ${san2}<br>
<br>
</tt>
<blockquote type="cite" cite="mid:A4765EB4FA674E6881C318711A64777D@tal">
<div><tt><font size="2">I happen to test many combination of
operating systems / settings,</font></tt></div>
<div><tt><font size="2">and it would be much faster to press Ctrl-B
and enter Win7G11,</font></tt></div>
<div><tt><font size="2">than to enter the whole chain of commands
required:</font></tt></div>
<div><tt><font size="2">> set gateway 192.168.1.11</font></tt></div>
<div><tt><font size="2">> sanboot iscsi:192.168.1.11::::win7</font></tt></div>
<div><tt> </tt></div>
<div><tt><font size="2">I'm familiar with the menu option, but the
number of iscsi targets involved would make it a mess to use a single
menu page, I'm also more comfortable with the command line.</font></tt></div>
<div><tt> </tt></div>
<div><tt><font size="2">One idea I had is to use an embedded script
to set a "root-directory" (batch scripts directory),</font></tt></div>
<div><tt><font size="2">and then, whenever an unknown-command will be
entered, we will chain "root-directory/unknown-command.pxe",</font></tt></div>
<div><tt><font size="2">this also requires that we will have a way to
abort the embedded script (where we set the root-dir variable) and
return to the command line.</font></tt></div>
<div><tt> </tt></div>
<div><tt><font size="2">if that sounds like too much, I can settle
for an </font><font size="2">"alias" command (alias Win7G11 sanboot
iscsi:192.168.1.11::::etc),</font></tt></div>
<div><tt><font size="2">again, we can use the embedded script, but we
need a way to return to the command line.</font></tt></div>
</blockquote>
<tt><br>
I hope this helps. I've replied using the gPXE mailing-list, rather
than the developers' list. I hope you don't mind.<br>
<br>
</tt><tt>Disclaimer: All claims and opinions are solely those of myself
and do
not and should not be perceived as representing the Etherboot nor the
gPXE projects in any way. Thank you for your understanding.<br>
<br>
- Shao Miller<br>
</tt>
</body>
</html>