If the project is interested, I patched gPXE to add another capability. I
was trying to make gPXE present to boot mac in the same format as pxelinux
IPAPPEND, but they didn't use colons. A lot of linux installers/netboot
code understands BOOTIF as-is, so this was required to evoke those features.
So I added a ${netX/machyp} so I could have hyphenated mac addresses like
pxelinux did. Also, to poster, I recommend you use netX instead of net0.
net0 will always be the 'first' nic, netX will be whatever nic you booted
from.if you really want a reliable per-host identifier rather than
per-interface, I would eye uuid a little more closely. You may encounter a
situation where predicting which interface would be 'net0' could be
difficult.
Here is the patch I used.
http://xcat.svn.sf.net/svnroot/xcat/xcat-dep/trunk/gpxe/gpxe-1.0.0-hyphenatedmachyp.patch
On Mon, Aug 2, 2010 at 7:21 PM, Doug Shove <dssh...@gmail.com> wrote:
> Hi,
>
> I'm wondering the best way to approach this issue: I have TFTP server
> running on a Windows box. I'd like to have a single file per MAC address on
> the TFTP server. gPXE clients would then retrieve the file:
> tftp://<server>/clients/${net0/mac}
>
> The problem is that Windows doesn't support colon ':' in the file name,
> however it does support dash '-'.
>
> What would be the best approach (in code or otherwise) to choose the format
> for a MAC address within gPXE?
>
>
> Thank you,
>
> Doug Shove
>
> _______________________________________________
> gPXE-devel mailing list
> gPXE-devel@etherboot.org
> http://etherboot.org/mailman/listinfo/gpxe-devel
>
>
_______________________________________________
gPXE-devel mailing list
gPXE-devel@etherboot.org
http://etherboot.org/mailman/listinfo/gpxe-devel
