- User Since
- Apr 24 2015, 6:10 PM (300 w, 12 h)
Mar 21 2019
Jun 2 2017
In my point of view I would like to use this flag in /etc/make.conf instead of patching local src. Having this flag allow users to use it no only for me. It's only a proposal, so the end of this story only up to you.
May 31 2017
It's the only one from pxeloader. I can safety remove the same from iPXE and in summary, during boot chain I have less a half of DHCP request in network. Let's say grain by grain...
May 27 2017
May 22 2017
May 19 2017
May 17 2017
tftpfs it's not bad, but you don't know what ipxe will do in the next commit. The problem is that we want to think about all.
May 14 2017
May 4 2017
May 3 2017
And the last one possible solution:
I based on the Intel's PXE Specification and there 66 exists.
May 2 2017
Please try to boot CURRENT over tftp protocol and without any third part software like iPXE.
May 1 2017
Until I go forward with your comments about the code I want to highlight it's not possible to support option 150, because we have to ask DHCP server for this option. PXE client (I mean network card firmware) never asks about option 150. I can't see any chance to use this non standard option but revert r314948 and always do DHCP request for everything. The second option is doing DHCP request in #ifdef LOADER_TFTP_SUPPORT directive, what is something bad too, because we want to have one universal loader for both (NFS and TFTP) protocols. The third option is to force DHCP request in ifdef directive when somebody really wants to do this. And the last one option - to leave support for option 150, because it has never appear in the documentation. I can't see any really good solution, now your move to comment.
Apr 26 2017
this change exactly provides compatibility with PXE standard, because in the PXE specification option 150 doesn't exist, but 66 does.
netproto variable and option 150 appears in r305125. Documentation and relnotes should be updated, but not by changing, because this part of loader never appers there (maybe I only can't find it).
Apr 24 2017
Mar 3 2017
Mar 2 2017
Mar 1 2017
Feb 14 2017
oshogbo's comments fixed and some new improvements
Jan 31 2017
Dec 14 2016
Dec 13 2016
It's should enough for backwards compatibility.
Dec 12 2016