After emerging tftp-hpa I discovered that tftpd expected stuff on stdin (think inetd), and in.tftpd was able to run in "daemon" mode (aka "standalone", "listen"). To check this 1) emerge tftp-hpa 2) start tftpd and check return code: /usr/sbin/tftpd -l -s /tmp; echo $? 3) start in.tftpd and check return code: /usr/sbin/in.tftpd -l -s /tmp; echo $? tftpd should return 0 if it is the real tftpd and port 69 is not in use. It will return 71 if port 69 is in use; use -a:<port> to change the listen port. in.tftpd should return 1 since it doesn't (though nothing would be wrong if it did, IMO) support listen mode. The opposite happend after emerging version 0.34. in.tftpd worked with -l, which isn't such a bad thing. tftpd failed with error 1 because it tried to operate on stdin as if it were a socket (and wrote a semi-mysterious error in /var/log/daemon). -Paul Komarek
it should also be moved into net-ftp
moved to net-ftp with a new update, but this bug still seems to exist.
Mass re-assign; this ebuild seems unmaintained.
0.40 is now stable
