From owner-freebsd-current  Thu Jul 18 13:14:13 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id NAA13922
          for current-outgoing; Thu, 18 Jul 1996 13:14:13 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA13917
          for <current@FreeBSD.org>; Thu, 18 Jul 1996 13:14:11 -0700 (PDT)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id NAA00586; Thu, 18 Jul 1996 13:13:42 -0700 (PDT)
To: Warner Losh <imp@village.org>
cc: Jonathan Lemon <jlemon@americantv.com>, current@FreeBSD.org
Subject: Re: various 'fetch' errors 
In-reply-to: Your message of "Thu, 18 Jul 1996 14:04:24 MDT."
             <199607182004.OAA02779@rover.village.org> 
Date: Thu, 18 Jul 1996 13:13:42 -0700
Message-ID: <584.837720822@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> Yes.  You are being naive.  :-) Let's say I wanted to fetch 10-20
> things.  And I have microbandwidth to the rest of the world.  I want
> them to happen sequentially rather than in parallel.  Let's also say I
> have multiple users that want to do this (say 1-2 each and there are 5

One of the nice things about UNIX is that you can string existing
tools together.  Putting all of the above into fetch strikes me as
overkill in the extreme and you'll never see me add anything as
ludicrous as this to it! :-)

						Jordna