Skip to contentSkip to conversation

dhcp vendor fields - support opt bootfile, ignore tftp server

PATCH New Murray.Jensen at csiro.au 2 participants 2 messages Jun 30, 2005 – Mar 12, 2006

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 dhcp vendor fields - support opt bootfile, ignore tftp server

This patch adds support for the dhcp vendor optional bootfile (#67). It also ignores the vendor tftp server name option (#66). Both of these are supplied by the DEC Tru64 Unix dhcp server (called "join"), and in the case of the bootfile, it is the only place the boot file name is supplied. There is a perfectly good, 128 byte, field in the main bootp/dhcp packet where the boot file name could have been stored, but it wasn't used - go figure. Cheers!

								Murray...
Signature · 20 lines
Murray Jensen, CSIRO Manufacturing & Infra. Tech.      Phone: +61 3 9662 7763
Locked Bag No. 9, Preston, Vic, 3072, Australia.         Fax: +61 3 9662 7853
Internet: Murray.Jensen at csiro.au

To the extent permitted by law, CSIRO does not represent, warrant and/or
guarantee that the integrity of this communication has been maintained or
that the communication is free of errors, virus, interception or interference.

The information contained in this e-mail may be confidential or privileged.
Any unauthorised use or disclosure is prohibited. If you have received this
e-mail in error, please delete it immediately and notify Murray Jensen on
+61 3 9662 7763. Thank you.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: DHCP-VEN.PAT
Type: text/x-patch
Size: 2204 bytes
Desc: dhcp-vendor-bootfile.patch
Url : http://lists.denx.de/pipermail/u-boot/attachments/20050630/5d5227e0/attachment.bin 
#1 lore raw

PATCH 1/1 dhcp vendor fields - support opt bootfile, ignore tftp server

Quoted 7 lines · In message <29183.1120112411@gerd> you wrote:

This patch adds support for the dhcp vendor optional bootfile (#67). It also ignores the vendor tftp server name option (#66). Both of these are supplied by the DEC Tru64 Unix dhcp server (called "join"), and in the case of the bootfile, it is the only place the boot file name is supplied. There is a perfectly good, 128 byte, field in the main bootp/dhcp packet where the boot file name could have been stored, but it wasn't used - go figure.

Applied, thanks.
But please provide a proper CHANGELOG entry next time.

Best regards,

Wolfgang Denk

Signature · 4 lines
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"Now here's something you're really going to like!"
- Rocket J. Squirrel