From owner-freebsd-arch@freebsd.org Mon Aug 8 17:44:11 2016 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6ADEDBB2ED9; Mon, 8 Aug 2016 17:44:11 +0000 (UTC) (envelope-from devin@shxd.cx) Received: from shxd.cx (mail.shxd.cx [64.201.244.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 579CF1648; Mon, 8 Aug 2016 17:44:11 +0000 (UTC) (envelope-from devin@shxd.cx) Received: from 50-196-156-133-static.hfc.comcastbusiness.net ([50.196.156.133]:62686 helo=[10.19.158.225]) by shxd.cx with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1bWne2-000J98-3O; Mon, 08 Aug 2016 16:43:18 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: Sparc64 doesn't care about you, and you shouldn't care about Sparc64 From: Devin Teske In-Reply-To: Date: Mon, 8 Aug 2016 10:44:07 -0700 Cc: Adrian Chadd , Michelle Sullivan , Anna Wilcox , freebsd-arch , Marius Strobl , Sean Bruno , Jordan Hubbard , sparc64@freebsd.org, Warner Losh , Devin Teske Content-Transfer-Encoding: quoted-printable Message-Id: <608A3403-D15D-4092-B097-15B30F600B97@freebsd.org> References: <64302b19-9f33-4267-af44-7fc30ea4bf3d@email.android.com> <56434F34.6040707@sorbs.net> <20160805153236.GA16908@funkthat.com> To: "K. Macy" X-Mailer: Apple Mail (2.2104) Sender: devin@shxd.cx X-Mailman-Approved-At: Mon, 08 Aug 2016 17:54:08 +0000 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2016 17:44:11 -0000 What luck, I was just gifted a Sparc64 1U rackmount Sun server. Not sure what to do with it since we shouldn't care about Sparc64. Is there a "latest version" that this hardware won't run? Admitting here = to not being up-to-date on this [particularly long-lived] thread. --=20 Devin=