From owner-freebsd-current@FreeBSD.ORG  Wed Jan 29 23:09:45 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 29F8E393
 for <freebsd-current@freebsd.org>; Wed, 29 Jan 2014 23:09:45 +0000 (UTC)
Received: from mail.ultra-secure.de (mail.ultra-secure.de [78.47.114.122])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 65DA11109
 for <freebsd-current@freebsd.org>; Wed, 29 Jan 2014 23:09:44 +0000 (UTC)
Received: (qmail 28179 invoked by uid 89); 29 Jan 2014 23:08:46 -0000
Received: from unknown (HELO ?192.168.1.201?)
 (rainer@ultra-secure.de@217.71.83.52)
 by mail.ultra-secure.de with ESMTPA; 29 Jan 2014 23:08:45 -0000
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: freebsd-update
From: Rainer Duffner <rainer@ultra-secure.de>
In-Reply-To: <1390662664.13404.75208481.39F16B29@webmail.messagingengine.com>
Date: Thu, 30 Jan 2014 00:07:24 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <38668639-4BD7-4FA4-B96F-4EA15F5518D7@ultra-secure.de>
References: <lblts0$9o1$1@ger.gmane.org>
 <CAJ5UdcO6V_YnyoJSA=JRL_D7vFzZ8yXcKnh2QcjNQDskbpE98w@mail.gmail.com>
 <5F09668C-0DEA-4074-A06C-BC4D29F92368@FreeBSD.org>
 <201401211149.45793.jhb@freebsd.org>
 <CAN6yY1uiNcWPuJL=O6osDhZci_YBXe7tRW0Nt_cUy25cCTbALQ@mail.gmail.com>
 <52E2C1BC.10202@allanjude.com> <20140125113236.GX86491@e-new.0x20.net>
 <1390662664.13404.75208481.39F16B29@webmail.messagingengine.com>
To: Mark Felder <feld@freebsd.org>
X-Mailer: Apple Mail (2.1827)
Cc: freebsd-current@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
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 23:09:45 -0000


Am 25.01.2014 um 16:11 schrieb Mark Felder <feld@freebsd.org>:

>=20
>=20
> On Sat, Jan 25, 2014, at 5:32, Lars Engels wrote:
>>=20
>>=20
>> 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?=20
>=20
> 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.


Apropos proxy:
freebsd-update does not work behind a proxy that requires =
authentication.
At least not with our proxy (which is a Sophos/Astaro =84threat =
management appliance").
That=92s OK for me, because I can talk the proxy-guys here into making =
an exception for my FreeBSD-servers - but It=92s really a nuisance =
because everything else (that uses libfetch) can use =
proxy-authentication.