Richard Bailey wrote: > The reason why I thought it might be an issue was because of the > description of atftpd in debian/ubuntu. Specifically this part: > > "Multi-threaded TFTP server implementing all options (option > extension and multicast) as specified in RFC1350, RFC2090, RFC2347, > RFC2348 and RFC2349." > > I was wondering if anyone on the list knew if the MediaMVPs, or the > H3, needed any one of these options mentioned in these RFCs.
I doubt it, but I don't know for certain. There are two places where the MVP accesses the TFTP server. One is via the Hauppauge boot firmware (loading the dongle), and the other is during mvpmc startup to transfer the "config" (startup script) and theme. The latter uses the simple tftp client supplied with BusyBox, which I doubt uses any extended features. I can't say what Hauppauge is doing in their code. What I say is that an MVP will boot fine using a TFTP server other than atftpd. On my Ubuntu box I switched from atftpd to tftpd (the one ported from BSD), because I found it to be a slightly less buggy implementation. > The description for tftpd-hpa says it implements extra options... I'd recommend turning up the debug level on tftpd-hpa, if you can, and see what is not working when you try and boot an MVP from it. Conversely, what do the LTSP people say is special about tftpd-hpa that can't be done by atftpd? -Tom ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
