Using scriptlet option?

[myxal]

(2018-03-15 08:44)NiKiZe Wrote:  Just as described in http://forum.ipxe.org/showthread.php?tid...98#pid4798
It sounds like it would be better for you to use some other dhcp option to send the values of those settings
and then pick them up in your normal script, you would add something like this to your script:
<snip>

EDIT: Just for the record, the correct dnsmasq configuration:

Code:

dhcp-option-force=<tag filters...>,128,"live-netdev=eth1"

to reference the value as ${128:string}, or

Code:

dhcp-option-force=<tag filters...>,encap:175,82,"live-netdev=eth1"

to reference the value as ${175.82:string}

Anyway, I think I found the closest thing to scriptlet documentation: http://etherboot.org/pipermail/gpxe-deve...00482.html

Quote:If the "scriptlet" NVO is set, gPXE will execute its value as a script
before executing any embedded script and before attempting to
autoboot. This allows users to override or augment compiled-in boot
behaviour by setting "scriptlet" using the gPXE command line
interface. Scriptlets may be up to 255 characters long, but may be limitted
by available NVO storage.

Useful scriptlets need not be long. Some examples are:
"ifopen net0\nsanboot ${net0/root-path}":
sanboot without DHCP, using NVO "ip", "netmask", and "root-path" settings.
"autoboot\nloopif 1"
autoboot, retrying forever, using the experimental "loopif" command.

Being able to modify boot behaviour without recompiling can be useful
to users under the following circumstances:
* The user does not have tools required to burn a ROM.
* The user cannot conveniently recompile because they use an OS
that cannot rebuild gPXE, or cannot reprogram ROMs.
* The user cannot conveniently access the web (for ROM-o-matic), because
they are in a secure facility without Internet access.
* The user cannot reprogram NICs without removing them from a machine.
(This is a big deal when you have hundreds of machines.)

---