From owner-freebsd-sparc64@FreeBSD.ORG Tue Apr 13 01:36:07 2010 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9D73106566B for ; Tue, 13 Apr 2010 01:36:07 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id A7A218FC08 for ; Tue, 13 Apr 2010 01:36:07 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 1A6EC8C085; Mon, 12 Apr 2010 20:36:07 -0500 (CDT) Date: Mon, 12 Apr 2010 20:36:07 -0500 From: Mark Linimon To: Miles Nordin Message-ID: <20100413013607.GA6417@lonesome.com> References: <20100324075709.GC13561@lonesome.com> <20100324223809.GA34342@alchemy.franken.de> <4BAB4AB9.2090908@buffalo.edu> <1269526260.2007.3.camel@main.lerwick.hopto.org> <20100325233558.GI20888@alchemy.franken.de> <4BACCC0C.7010401@freebsd.org> <20100410015309.GB19697@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Mark Linimon , freebsd-sparc64@freebsd.org Subject: Re: freebsd-update(8) under sparc64? Why is it not available? X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Apr 2010 01:36:07 -0000 On Mon, Apr 12, 2010 at 05:11:31PM -0400, Miles Nordin wrote: > Colin's position is totally ridiculous: people offer build resources > of exotic, heavy, power-hungry hardware to the FreeBSD project, which > already has scripts and frameworks for producing timely builds, but he > believes these offers are conterproductive [...] The problem is that we're effectively guaranteeing that bits pushed out via freebsd-update are secure. Our traditional view is that machines that are loaned to us aren't sufficiently secure for us to be able to stand behind that guarantee. Right now the machines used to produce those bits are dedicated to that purpose and that purpose only, and are physically and logistically secure. If someone wants to donate a sufficiently capable sparc64 machine to the project that can be installed under similar constraints, I'm all ears. Right now we don't have one. mcl