From owner-freebsd-sparc64@FreeBSD.ORG Fri Apr 9 05:12:59 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 1922A106566C for ; Fri, 9 Apr 2010 05:12:59 +0000 (UTC) (envelope-from carton@Ivy.NET) Received: from sakima.Ivy.NET (sakima.Ivy.NET [69.31.131.60]) by mx1.freebsd.org (Postfix) with ESMTP id A15288FC0C for ; Fri, 9 Apr 2010 05:12:58 +0000 (UTC) Received: from castrovalva.Ivy.NET (castrovalva.Ivy.NET [69.31.131.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sakima.Ivy.NET (Postfix) with ESMTP id 8CC85A80E5 for ; Fri, 9 Apr 2010 01:12:57 -0400 (EDT) Received: by castrovalva.Ivy.NET (Postfix, from userid 405) id 710EF12FD0D; Fri, 9 Apr 2010 01:12:57 -0400 (EDT) To: freebsd-sparc64@freebsd.org References: <4BA9C0AC.3080801@wooh.hu> <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> From: Miles Nordin MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: multipart/signed; boundary="pgp-sign-Multipart_Fri_Apr__9_01:12:57_2010-1"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 09 Apr 2010 01:12:57 -0400 In-Reply-To: <4BACCC0C.7010401@freebsd.org> (Colin Percival's message of "Fri, 26 Mar 2010 08:00:28 -0700") Message-ID: User-Agent: T-gnus/6.17.2 (based on No Gnus v0.2) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.4 (alpha--netbsd) MULE/5.0 (SAKAKI) 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: Fri, 09 Apr 2010 05:12:59 -0000 --pgp-sign-Multipart_Fri_Apr__9_01:12:57_2010-1 Content-Type: text/plain; charset=US-ASCII >>>>> "cp" == Colin Percival writes: cp> it would "train" people to use binary updates rather than cp> source updates, and the times when they would need to wait -- cp> time-sensitive security advisories -- are exactly the times cp> when they shouldn't wait. hilarious. wait, no yeah, actually Colin I have your security update list feeding directly into my phone, and when one of your updates comes out I drop whatever I'm doing and spin up my quad USIII cluster, which I keep on-hand but powered off in a ``spare'' rack in lower Manhattan to support my Netra X1 by running builds for me. I keep thinking, oh, maybe I'll get rid of the ``spare'' rack, I'm not sure. Or maybe I'll keep it. I can't decide. I could go either way. I don't really even notice whether I keep it or not. I suppose if I got into the habit of being trained to do binary upgrades of my X1 I might notice the rack was unnecessary and ditch the four power-guzzling 50kg machines inside it. Yeah, and that would be a mistake, because it would leave the critical services on my X1 vulnerable for precious extra hours which evil hackers could use to write sparc64 shell code and compromise critical pieces of infrastructure! good thinking, good thinking. I can always count on the crack team of experienced blokes on the BSD project to forsee the unexpected. dunno what I'd do without your valuable foresight. --pgp-sign-Multipart_Fri_Apr__9_01:12:57_2010-1 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (NetBSD) iQCVAwUAS763WYnCBbTaW/4dAQIZZwP/dc/cp7PzrH3dbSGBrH5UKGtHEbybb+jj pd1ZKPPFvM6qBbF0lAeagrhkUIFa22NEV5LyAmZv907i16LQClfb3EjiitoYIYGS 2llzJ1LKTRSyN6IaJ9/fRSRCaWUcbk4gkRuAmQtVyNIpjWZbdDENIG+KpS2StDmM S5UA+3oXl6g= =kTDA -----END PGP SIGNATURE----- --pgp-sign-Multipart_Fri_Apr__9_01:12:57_2010-1--