[gPXE] gPXE Feature Request: assigning customcommandstoexecute batch files

Miller, Shao Shao.Miller at yrdsb.edu.on.ca
Mon Feb 8 07:26:09 EST 2010


I don't quite know what you mean by "default to autoboot()"...

#!gpxe
set space:hex 20

# Commands we like
set sanboot_cmd sanboot
set chain_cmd chain

# Append a space
set sanboot_cmd:hex ${sanboot_cmd:hex}:${space:hex}
set chain_cmd:hex ${chain_cmd:hex}:${space:hex}

# SAN targets
set win7 iscsi:192.168.0.100::::foo:win7
set winxp iscsi:192.168.0.100::::foo:winxp

# Prepend sanboot command
set win7:hex ${sanboot_cmd:hex}:${win7:hex}
set winxp:hex ${sanboot_cmd:hex}:${winxp:hex}

# Chain targets
set linux http://webserver/vmlinuz

# Prepend chain command
set linux:hex ${chain_cmd:hex}:${linux:hex}

# Tell user about choices
echo Available boot options for CLI: win7, winxp, linux
echo Surround your choice with $ { and } characters, no spaces.

# Default to autoboot
autoboot

- Shao Miller

-----Original Message-----
From: gpxe-bounces at etherboot.org on behalf of Tal Aloni
Sent: Mon 2/8/2010 6:27 AM
To: gpxe
Subject: Re: [gPXE] [gPXE-devel] gPXE Feature Request: assigning customcommandstoexecute batch files
 
thanks, nice to know,
note that the way you suggested can't default to autoboot().
 
Tal


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://etherboot.org/pipermail/gpxe/attachments/20100208/23d3baf6/attachment.html 


More information about the gPXE mailing list