Re: [Etherboot-developers] DHCP option 175

[<ebi...@ln...>]

ke...@us... (Ken Yap) writes:

> >Etherboot will send PCI ID inside vendor-encapsulated-options.
> 
> Another advantage of using VEO is that you get a whole namespace with
> it. If later it's decided that it's a good idea to send the CPU type or
> the memory size, you can allocate further tags in that namespace rather
> than agonise about taking option 176, 177, etc.

As a general rule we should be passing enough information that
a smart host can verify an image will load, and be able to continue
communicating with where it came from.  (So it can load additional
components etc).

To that end I suspect enventually we will need, (especially if we
standardize this, and start working with other implementations).
- CPU family. (X86, Alpha, Hammer, Itanium, PPC, ...)
- Image types accepted. (Tagged, ELF, a.out, COFF, ...)
- Network card (PCI ID or equivalent)
- Usable RAM (roughly the e820 memory map)
- Protocols supported (TFTP, NFS, ...)
   (Though for this a refusing to ack a filename that asks for this
    may be reasonable.)


Eric