From owner-freebsd-questions@FreeBSD.ORG  Mon Jan 31 06:06:17 2005
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A99B416A4CE
	for <questions@freebsd.org>; Mon, 31 Jan 2005 06:06:17 +0000 (GMT)
Received: from dd5114.kasserver.com (dd5114.kasserver.com [83.133.48.29])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3DF0B43D2F
	for <questions@freebsd.org>; Mon, 31 Jan 2005 06:06:17 +0000 (GMT)
	(envelope-from malingo@6b6.com)
Received: from golulu.logelhorst.de (dsl-084-057-001-066.arcor-ip.net
	[84.57.1.66])
	by dd5114.kasserver.com (Postfix) with ESMTP id 2E3BD9C19C
	for <questions@freebsd.org>; Mon, 31 Jan 2005 07:06:15 +0100 (CET)
Received: by golulu.logelhorst.de (Postfix, from userid 1000)
	id 5C02392; Mon, 31 Jan 2005 07:06:51 +0100 (CET)
From: Ram Caturvedi <malingo@6b6.com>
To: questions@freebsd.org
Date: Mon, 31 Jan 2005 07:06:50 +0100
User-Agent: KMail/1.7.1
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200501310706.50951.malingo@6b6.com>
Subject: German Mirrors?
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jan 2005 06:06:17 -0000

Hi,

it appears that no German mirror has a synchronized yet, so that it is not 
possible to get FreeBSD-4.11-RELEASE from one of those. Probably this comes 
from a broken update hierarchy, so maybe someone should try to fix that...

Regards
k.j.