From owner-freebsd-current Tue Jan 6 18:49:33 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA26836 for current-outgoing; Tue, 6 Jan 1998 18:49:33 -0800 (PST) (envelope-from owner-freebsd-current) Received: from lsd.relcom.eu.net (ache@lsd.relcom.eu.net [193.124.23.23]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA26817 for ; Tue, 6 Jan 1998 18:49:16 -0800 (PST) (envelope-from ache@lsd.relcom.eu.net) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.8/8.8.8) id FAA10081; Wed, 7 Jan 1998 05:49:01 +0300 (MSK) (envelope-from ache) Date: Wed, 7 Jan 1998 05:49:00 +0300 (MSK) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= X-Sender: ache@lsd.relcom.eu.net To: Satoshi Asami cc: jkh@time.cdrom.com, current@FreeBSD.ORG Subject: Re: Time to retire fetch? In-Reply-To: <199801051140.DAA10749@baloon.mimi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 5 Jan 1998, Satoshi Asami wrote: > To me, 3 sounds like the best approach. However, we need to make sure > fetch an ftp are compatible in all senses (e.g., whether you include > the full path when you go to a on-the-fly tarballing site). I > remember ache mumbling something about non-anonymous ftp too. fetch now supports HTTP 1.1, user:password auth for both ftp and http and restart feature for both ftp and http. Next thing is TCP optimization (also with conflict with some sites, which can be resolved by adding an option). If new ftp not provide the same features (I don't check at this moment), my word is definitely against switching. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/