On Tue, Feb 25, 2003 at 12:13:38PM -0500, Nathan J. Williams wrote:
> Alex <xela@MIT.EDU> writes:
> 
> > Some Intel PXE ROMs have a bug that results in the bootfile name
> > being sent to tftpd with an 0xff appended to the end of the
> > filename.  This results in the machine not booting because the
> > boot file couldn't be found, and a fair bit of wasted sysadmin 
> > time.
> 
> Your workaround prevents the sysadmins from noticing that their PXE
> ROMs are broken and applying negative reinforcement to the vendor. I
> agree with what others have said that having the ability to debug this
> kind of lossage is more important than a workaround for one specific
> case. What if the next rev of this buggy PXE ROM appends a 0xfe rather
> than 0xff?


I agree - the thing to do is to ensure that tftpd's error message
has the 0xff byte 'suitably' escaped (probably even if 0xff the the
printable character ij or y").  The sysadmin can always
link the actual file to that name (isn't that the way you find the
filename that is being requested anyway?)

	David

-- 
David Laight: david@l8s.co.uk