From owner-freebsd-current@FreeBSD.ORG Thu Jan 30 04:37:55 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 25C2F146 for ; Thu, 30 Jan 2014 04:37:55 +0000 (UTC) Received: from mail-pd0-f169.google.com (mail-pd0-f169.google.com [209.85.192.169]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E87471041 for ; Thu, 30 Jan 2014 04:37:54 +0000 (UTC) Received: by mail-pd0-f169.google.com with SMTP id v10so2560723pde.14 for ; Wed, 29 Jan 2014 20:37:48 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=Bm0ylOHSaKOES9Odt+J6l3Pm0CCHJdGPizaravJomhA=; b=OPDlNwqdF1XewCy2VbIi8cENqDo3btCDML98Bse1YqjPwJoEXtBglgYh2XBnn0invt 2pAtXqyr+ShPVw2ip3ZJX5nz0Pk1gc8vqSvXD6fiDtyAwyeoYsmi+u4EsrcRXfdu1qK5 UgghIj3o2LNNeM6NX/xtdm9exE0h3pwIP0AHug2bb+HP6/H2SEnKrUr6L58mvrnJgH+e PzcCPEJ52QcXm7jdxiBE2Ey0aKRQGZIWYuxwHQi2Yu3m39/F5Lx+XIDiHK2Z8/Oeqmfs TW7St4Jpi8uiQUDOj0L1oZYAlmQV2cmDfzH+uoVpgyHynF38cOqjkRTowyfZ0wWz0hoc Ll6Q== X-Gm-Message-State: ALoCoQmgy83vfjYT3xS8OUlIt0pd9liUWtKqcwYGQ7jtS9vMChmFk+EZJrU75XlDOtsqUrkHc7Q1 X-Received: by 10.66.122.201 with SMTP id lu9mr12090253pab.40.1391056668620; Wed, 29 Jan 2014 20:37:48 -0800 (PST) Received: from [192.168.1.2] (c-24-6-182-22.hsd1.ca.comcast.net. [24.6.182.22]) by mx.google.com with ESMTPSA id pq1sm12609997pbc.8.2014.01.29.20.37.46 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 29 Jan 2014 20:37:47 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: freebsd-update From: Tim Kientzle In-Reply-To: <20140129205157.GB86491@e-new.0x20.net> Date: Wed, 29 Jan 2014 20:36:59 -0800 Content-Transfer-Encoding: 7bit Message-Id: <9EBC9714-47D9-42FD-9236-04ADF7868EEE@kientzle.com> References: <5F09668C-0DEA-4074-A06C-BC4D29F92368@FreeBSD.org> <201401211149.45793.jhb@freebsd.org> <52E2C1BC.10202@allanjude.com> <20140125113236.GX86491@e-new.0x20.net> <1390662664.13404.75208481.39F16B29@webmail.messagingengine.com> <20140129205157.GB86491@e-new.0x20.net> To: Lars Engels X-Mailer: Apple Mail (2.1827) Cc: FreeBSD current , cperciva@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 04:37:55 -0000 On Jan 29, 2014, at 12:51 PM, Lars Engels wrote: > On Sat, Jan 25, 2014 at 09:11:04AM -0600, Mark Felder wrote: >> >> >> On Sat, Jan 25, 2014, at 5:32, Lars Engels wrote: >>> >>> >>> Also using freebsd-update behind a proxy is really slow. Even with a >>> very fast internet connection (normally download rates ca. 3 MBytes / s) >>> downloading all the tiny binary diff files took more than 8 hours. >>> Maybe freebsd-update's backend could create a tarball of all those diffs >>> and provide this? >> >> Even streaming the tar instead of waiting for the freebsd-update server >> to produce the tarball would be an improvement. I have no experience >> doing that over a WAN but I don't see why it would be unreliable. I implemented an export capability for $WORK last year that built and streamed a Zip archive on the fly. It worked rather well even when the archives were multiple gigabytes with tens of thousands of entries. Tim