From owner-freebsd-ports  Sat Dec  2 04:19:11 1995
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id EAA09737
          for ports-outgoing; Sat, 2 Dec 1995 04:19:11 -0800
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id EAA09701
          for <FreeBSD-ports@freebsd.org>; Sat, 2 Dec 1995 04:18:56 -0800
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id EAA00888; Sat, 2 Dec 1995 04:18:28 -0800
Date: Sat, 2 Dec 1995 04:18:28 -0800
Message-Id: <199512021218.EAA00888@silvia.HIP.Berkeley.EDU>
To: jmz@cabri.obs-besancon.fr
CC: chuckr@glue.umd.edu, FreeBSD-ports@freebsd.org
In-reply-to: <9511291252.AA03916@cabri.obs-besancon.fr> (message from Jean-Marc Zucconi on Wed, 29 Nov 95 13:52:47 +0100)
Subject: Re: misc/colorls
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-ports@freebsd.org
Precedence: bulk

 * I am also behind a phone line (and sometimes at 2400bps) :-)
 * I wrote a ftpget replacement, and it has a (primitive) progression
 * indicator, it should work if you are behind a firewall, and is
 * compatible with ncftp. The program is very simple since it uses the
 * ftp code in src/release/sysintall/. Interested?

Yes!

We really need a little program that does only what we need, that we
can understand, and fix easily.  There is no need for interactive
mode, for instance.  All we need is an ability to fetch a file even
from behind the firewall, optionally renaming it, and be able to deal
with wu-ftpd's auto-packing.

(I hope I didn't forget something else.)  If yours can do that, let's
try it out!

Satoshi