<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000'>I would REALLY like the ability to load in snponly.efi . It would certainly make it very easy for me to provide the single unified installation menu that I have for all hardware. It really sucks that this isn't in the main code base.<br><br><hr id="zwchr"><blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div dir="ltr"><div>I restored snponly.efi function with a PoC patch:<br><a href="https://git.ipxe.org/vendor/xcat/ipxe.git/commitdiff/19447d9c39e06c3d5aabd198736cd23d8e40c870" target="_blank">https://git.ipxe.org/vendor/xcat/ipxe.git/commitdiff/19447d9c39e06c3d5aabd198736cd23d8e40c870</a><br>
<br></div>I haven't gotten around to cleaning it up, it could be much better.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 3, 2013 at 8:19 AM, Michael Brown <span dir="ltr"><<a href="mailto:mbrown@fensystems.co.uk" target="_blank">mbrown@fensystems.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Thursday 02 May 2013 23:14:47 Duane Voth wrote:<br>
> I am right in expecting the snponly ipxe to work nicely with existing<br>
> network devices right? Or perhaps this usage impacts the question above?<br>
<br>
</div>Quite possibly not. EFI doesn't have a clean model for multiple users of an<br>
SNP interface.<br>
<div class="im"><br>
> Last, at what point does snp ipxe plug into the uEFI stack? Is the ipxe<br>
> dhcp config separate from the EFI dhcp client? (I have noticed two<br>
> different IP addresses being allocated for this same NIC/MAC)<br>
<br>
</div>iPXE's TCP/IP stack is entirely separate from the EFI TCP/IP stack. EFI knows<br>
nothing about addresses obtained using DHCP inside iPXE.<br>
<div class="im"><br>
> Could ipxe use more of the existing protocols now that edk2 is more stable?<br>
<br>
</div>It could, but it's not going to. iPXE is going to deliberately avoid the EDK2<br>
facilities and limitations. See <a href="http://ipxe.org/efi/vision" target="_blank">http://ipxe.org/efi/vision</a> for the reason why.<br>
<div class="HOEnZb"><div class="h5"><br>
Michael<br>
_______________________________________________<br>
ipxe-devel mailing list<br>
<a href="mailto:ipxe-devel@lists.ipxe.org" target="_blank">ipxe-devel@lists.ipxe.org</a><br>
<a href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" target="_blank">https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</a><br>
</div></div></blockquote></div><br></div>
<br>_______________________________________________<br>ipxe-devel mailing list<br>ipxe-devel@lists.ipxe.org<br>https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel<br></blockquote><br><br><br>-- <br><div><span name="x"></span>James A. Peltier<br>Manager, IT Services - Research Computing Group<br>Simon Fraser University - Burnaby Campus<br>Phone : 778-782-6573<br>Fax : 778-782-3045<br>E-Mail : jpeltier@sfu.ca<br>Website : http://www.sfu.ca/itservices<br><br>“A successful person is one who can lay a solid foundation from the bricks others have thrown at them.” -David Brinkley via Luke Shaw<span name="x"></span><br></div></div></body></html>