Re: [Etherboot-developers] Patch for TFTP-multicast released

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

>I got the lastest sources and made up a diff file against them - I'm not sure
>if all that stuff compiles, or if it breaks anything for you, but apply that 
>patch to the sources in etherboot 5.1 -not forgetting the backup option of 
>"patch" - and copy proto_tftm.c to that dir, so you get the following new 
>possibilities in "Config":
>
>-DURI_SUPPORT
>	you will need this anyway
>-DURI_SUPPORT_FILE
>	so you can use filenames like "file:/disk/0" and so on.
>-DURI_SUPPORT_TFTP
>	so "tftp:///filename" will be recognised.
>-DURI_SUPPORT_NFS
>	as well
>-DURI_SUPPORT_SLAM
>	so "x-slam://" URIs are recognised. Ask Eric how far his slam code wen
>t, you
>	probably want to set -DDOWNLOAD_PROTO_SLAM too.
>-DURI_SUPPORT_TFTM
>	so "x-tftm://server-ip/filename" can be recognised. You will also have
> to
>	set the -DDOWNLOAD_PROTO_TFTM option for this to work.

Please rework it so that only URI_SUPPORT needs to be defined and then
it implies URI_SUPPORT_XXX depending on whether DOWNLOAD_PROTO_XXX has
been defined. I don't want 5 additional options when 1 will do.

>These URIs can be extended to allow specification of anti-standard UDP ports 
>or another server's IP (no DNS [for now?], so no hostnames). For TFTM, 
>servername works fine (don't know if it's even required to be present !? - no
>matter, bugfixing tftm will be necessary for some time)

Please publish a specification of the URIs. Do you take the TFTP server
from only the DHCP siaddr field?  I don't want a redundant specification
of a different server when they should be using next-server in
dhcpd.conf if they want a different TFTP server.