Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
relative tftp path for embedded script, pxelinux.0 behaviour
2012-07-22, 21:54 (This post was last modified: 2012-07-22 21:56 by aka.)
Post: #3
RE: relative tftp path for embedded script, pxelinux.0 behaviour
No.

User untar my distributive somewhere under tftp root. undionly.kpxe and default.ipxe stored in this distributive. I didn't know where user untar it while I write default.ipxe. In your example, you know path. I don't know the path. Then user write path to undionly.kpxe into 067 dhcp option. For example, 067 dhcp is: diskless/wt5/5.1.16/undionly.kpxe

pxelinux.0 will automatically look at 067 and search config in diskless/wt5/5.1.16/, not in tftp root. So user can untar files from distributive anywhere he want, and pxelinux.0 will find config.

I need something like this (docs of my dream):

Quote:If this command is executed from within an embedded into undionly.kpxe iPXE script, then the URI will be interpreted as being relative to the URI of the undionly.kpxe downloaded from. For example, if the script embedded into undionly.kpxe downloaded from tftp as "any/path/in/tftp/undionly.kpxe" contains the line
chain default.ipxe
then iPXE will download and boot "any/path/in/tftp/default.ipxe" from the same tftp server.
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: relative tftp path for embedded script, pxelinux.0 behaviour - aka - 2012-07-22 21:54



User(s) browsing this thread: 3 Guest(s)