Date: Sun, 27 May 2018 16:32:43 +0200 From: Rainer Duffner <rainer@ultra-secure.de> To: Randy Bush <randy@psg.com> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: freebsd-update: cannot open patchlist Message-ID: <0811992D-9ADE-4B46-BA2C-0198149930EE@ultra-secure.de> In-Reply-To: <m2y3g5qike.wl-randy@psg.com> References: <m2bmd1svj3.wl-randy@psg.com> <623D218F-A36F-40DD-9BD2-592E476051E8@ultra-secure.de> <m2y3g5qike.wl-randy@psg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 27.05.2018 um 16:28 schrieb Randy Bush <randy@psg.com>: >=20 > indeed, that fixes it. thank you. ;-) BTDTGTT This is (or was) especially a problem with ezjail=E2=80=99s use of = freebsd-update. Most of the time, freebsd-update works - but when it gets confused, the = quickest solution is often to start from scratch. Which is a real pain if you need to download through a proxy that = doesn=E2=80=99t do http-pipelining (like the Sophos UTM n=C3=A9e Astaro = devices). IIRC, there=E2=80=99s still no way to disable that behavior.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0811992D-9ADE-4B46-BA2C-0198149930EE>