[gPXE] DHCP Client ID in gPXE 1.0.0?

[Michael Brown]

On Friday 19 March 2010 20:17:13 Shao Miller wrote:
> But I often get stuck in "analysis paralysis" during thought processes
> regarding abstraction of code...  Where is the balance between gPXE
> being a network boot-loader and being an OS kernel itself?  Since not
> 100% of users' needs can be met within the constraint space, whose needs
> get left out?  If it's going to be a kernel of sorts for features to
> plug in to, it will have to be small and fast, where usually you "pick
> one".  If it's going to be a highly optimized atomic package of
> features, it'll be an assembly...?  Ha!

FWIW, I've generally found that the primary constraint is the inability to 
preempt threads of execution, which in turn arises because we don't have 
enough dynamically allocatable RAM for each thread to have its own stack 
context.  This leads to designs such as the data-xfer interface, where code 
must be prepared to receive data via what is essentially a callback method, 
rather than by blocking in a read()-type call.

Michael