#193 Issue closed: Extend PXE_TFTP_PATH and PXE_CONFIG_PATH to support url

Labels: enhancement, fixed / solved / done, sponsored

pavoldomin opened issue at 2013-01-29 19:00:

Enhancement request:
Would be great if PXE_TFTP_PATH and PXE_CONFIG_PATH support URL syntax, similar to OUTPUT_URL, such that PXE kernel, initrd, message, menu and links can be uploaded directly to remote server.

See also #192

gdha commented at 2013-02-01 12:15:

I wonder which role OUTPUT_URL could play with PXE? Should we expand the possibilities of PXE_TFTP_PATH and PXE_CONFIG_PATH or not?
Please share your thoughts...

pavoldomin commented at 2013-02-01 14:02:

I'd say, if OUTPUT_URL is defined in the same time as PXE_TFTP_PATH and PXE_CONFIG_PATH, than both are honored, i.e. ${RESULT_FILES[@]} are uploaded to OUTPUT_URL. In the same time, menu and MAC symlinks go to PXE_CONFIG_PATH url and kernel and initrd go to PXE_TFTP_PATH url.

With this

  • default works same as now.
  • if user wants to upload everything required for boot to one place, he'll define OUTPUT_URL
  • if user wants to upload pxe output stuff directly to bootp/tftp server, he'll define PXE_{TFTP|CONFIG}_PATH URLs.

Would be more readable than, to rename PXE_{TFTP|CONFIG}_PATH to PXE_{TFTP|CONFIG}_URL.

gdha commented at 2013-02-04 12:34:

@pavoldomin sounds logical and acceptable. Looking forward to the pull request.

gdha commented at 2013-07-03 11:45:

@pavoldomin is this issue still relevant?

pavoldomin commented at 2013-09-10 07:07:

I have had no time to dig into this yet, sorry. I suppose it is still relevant - as soon as recent lftp commits have not addressed it.

gdha commented at 2016-10-24 16:51:

I am currently addressing this topic

gdha commented at 2016-11-24 08:33:

@pavoldomin perhaps an interesting feature you would like to test?

gdha commented at 2016-12-31 10:12:

It works for me, closing this one. If problems arise I'm pretty sure a new issue will be opened.

[Export of Github issue for rear/rear.]