>> what's the difference between the two methods ?
When running FTPd as a daemon, you can't configure access restriction with TCP Wrappers. It also takes more resource when launching multiple daemons. Unlike proftpd and apache where you can configure those when running out of inetd.
BTW, I don't trust inetd and I have it completely disabled for all my *BSD boxes. If I have a need to run FTP server, I either run Proftpd standalone or use a inetd replacement -> tcpserver
Like I always said, djb (qmail author) makes the most secure software on earth. If there exists a djb software that is intended to be a replacement (except publicfile to replace Apache), follow his advice and just do so. Just to name a few:
- dnscache to replace BIND cache
- tinydns+axfrdns to replace BIND authoritative DNS server
- qmail to replace sendmail
- tcpserver to replace inetd
- multilog to replace syslogd