[syslinux] Distilling down a small set of useful system data
Alexander,Jeff
Jeff.Alexander at wwt.com
Wed Apr 27 15:22:12 PDT 2011
If I am understanding this correctly, this may end up being what would allow us to move forward with booting over http in production. If 90% of our systems boot just fine using our http method, having something that would allow us to specify that a subset of models boot from an alternative method would be awesome. Those models would be the ones that were found to be incompatible using the http method.
-----Original Message-----
From: syslinux-bounces at zytor.com [mailto:syslinux-bounces at zytor.com] On Behalf Of H. Peter Anvin
Sent: Wednesday, April 27, 2011 5:00 PM
To: For discussion of Syslinux and tftp-hpa
Subject: Re: [syslinux] Distilling down a small set of useful system data
On 04/27/2011 02:48 PM, H. Peter Anvin wrote:
> On 04/27/2011 02:41 PM, Erwan Velu wrote:
>> If we speak about conditional booting, cpu is a very common requested
>> feature. Ifcpu.c32 exists wheres a conditional ifdmi.c32 doesn't.
>
> Yes, that's true, but ifcpu64 was not sufficient. Sending *ALL* the
> data that ifcpu hinges in an unsolicited reply is a *lot*.
>
> Therein lies the dilemma...
I do note that DMI-based configuration file selection *has* been a very
commonly requested feature; not so much for conditional boot but for
conditional menus.
There might be a difference there, I don't really know. I do recognize
this as a shortcoming, I just don't have a good answer at this point.
Ideas would be appreciated...
-hpa
_______________________________________________
Syslinux mailing list
Submissions to Syslinux at zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.
More information about the Syslinux
mailing list