Re: [Etherboot-developers] Q: Multiple drivers.

[<ke...@us...>]

>I have in mind a "PXE nuker" bootable image which runs on new COTS
>hardware; it registers the new box with the local admin database,
>reports which nics and other hardware are there and performs any local
>tweaking that we'd like, e.g. flash nic and/or system rom with LinuxBIOS
>and or Etherboot, and insert whatever is needed in the way of local
>state. Then it would run tests and exercisers, report that everything's
>OK and initiate an appropriate system install. Why not have a local
>rom-o-matic on the server which magics up a bespoke image for the system
>at install? Indeed, why not check for updates (and reflash if needed) at
>*every* reboot?

What you implement at your site is your business. If you want it badly
enough, you can patch the source yourself, maybe as part of the
rom-o-matic process. If experience shows that this is of use to a
significant portion of the user population, I'll consider it for
inclusion.