|
From: Michael B. <mb...@fe...> - 2002-12-13 09:46:51
|
On 12 Dec 2002, Eric W. Biederman wrote: > > Not quite sure what you mean here. Etherboot will accept any of the old > > Etherboot-specific options inside an etherboot-encapsulated-options field > > (i.e. a dhcp option 150). > But all such options have been removed from the core of etherboot, > with I believe the removal of the image menu. True enough; I was looking at the 5.0 code which still has plenty. > Options always interpreted: > RFC1533_PAD > RFC1533_END > RFC1533_EXTENSIONPATH /* STD tftp file name of more options */ > Options that are never used in encapsulated options: > RFC1533_NETMASK /* Standard */ > RFC1533_GATEWAY /* Standard */ > RFC1533_VENDOR /* Vendor encapsulated options */ > RFC2132_MSG_TYPE /* Standard */ > RFC2132_SRV_ID /* Standard */ > RFC1533_HOSTNAME /* Standard */ > RFC1533_VENDOR_ETHERBOOT_ENCAP /* Only truly etherboot specific option */ > Options only interpreted in encapsulated options: > RFC1533_VENDOR_MAGIC /* Only option really used.. */ > RFC1533_VENDOR_HOWTO /* FreeBSD only */ > RFC1533_VENDOR_KERNEL_ENV /* FreeBSD only */ > The only place etherboot specific options show up is in the code of mknbi.... Etherboot-specific options 175 (and now also 177) are used as well, to pass information to the DHCP server inside an etherboot-encapsulated- options field. Michael |
