About TFTP

[Eygene Ryabinkin]

Tue, May 27, 2014 at 10:12:40PM +0800, Niu Zhixiong wrote:
> I want to modify the source code of TFTP. However it is invoked by
> inetd. I really need a standalone service of TFTP without inetd.

Why?  Inetd provides network pipe and connection initiation for
TFTP daemon and then it acts on the "cooked" socket for the port 69,
but does the rest of communication by itself, including opening
data connection back to the client.

> But, when a start tftpd without inetd. it says recvfrom: Socket
> operation on non-socket.

Because tftp daemon expects its standard input and output to be
network sockets.

> Could someone give me some suggestion to start tftpd without inetd?

FreeBSD stock TFTP daemon doesn't support this.  You may probably
look at the ports collection (/usr/ports/net) and software with
tftp in its name: there are at least 3 packages that look like
TFTP daemon.  But first I'd reconsider the need to drop inetd
from the game.  Or, if you're up to some coding, you can extend
our base tftp daemon with stand-alone capabilities.
-- 
Eygene Ryabinkin                                        ,,,^..^,,,
[ Life's unfair - but root password helps!           | codelabs.ru ]
[ 82FE 06BC D497 C0DE 49EC  4FF0 16AF 9EAE 8152 ECFB | freebsd.org ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 358 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-net/attachments/20140527/bcf5225d/attachment.sig>