From owner-freebsd-stable@freebsd.org Mon Oct 24 06:58:51 2016 Return-Path: Delivered-To: freebsd-stable@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 55654C1FE63 for ; Mon, 24 Oct 2016 06:58:51 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E5C7D39D for ; Mon, 24 Oct 2016 06:58:50 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [217.29.44.10]) by gate2.intern.punkt.de with ESMTP id u9O6wle9066025; Mon, 24 Oct 2016 08:58:47 +0200 (CEST) Received: from [217.29.44.130] ([217.29.44.130]) by hugo10.ka.punkt.de (8.14.2/8.14.2) with ESMTP id u9O6wlDF064457; Mon, 24 Oct 2016 08:58:47 +0200 (CEST) (envelope-from hausen@punkt.de) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: boot0cfg on does not set default selection on gmirror device From: "Patrick M. Hausen" In-Reply-To: <20161024133403.D6806@sola.nimnet.asn.au> Date: Mon, 24 Oct 2016 08:59:17 +0200 Cc: freebsd-stable Content-Transfer-Encoding: quoted-printable Message-Id: <7273E6C8-9462-4389-95B1-D94A15B5BC15@punkt.de> References: <14FD5FE6-6277-4EBE-8EE9-630A735F8BEA@punkt.de> <54B556F6-B834-4B0C-A9A4-90B9AD80A668@punkt.de> <20161022140755.S6806@sola.nimnet.asn.au> <20161024133403.D6806@sola.nimnet.asn.au> To: Ian Smith X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 06:58:51 -0000 Hi, all, > Am 24.10.2016 um 04:50 schrieb Ian Smith : >=20 > On Sun, 23 Oct 2016 15:53:59 +0200, Patrick M. Hausen wrote: >=20 >> Actual reboot of this production machine in two weeks when we run our >> regular updates. But I expect that to "just work". >=20 > Warner expected the existing boot0cfg code to "just work" too. And it=20= > does, except that the upgrades to it failed to include a method to fix=20= > existing installations retrospectively! If the boot0 code 2.0 was severely broken, don't you think we would have noticed? ;-) One more thing, I just checked: the machines for which it did work all the time are indeed younger and all have the 2.0 bootcode. Thanks for your help. Patrick --=20 punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 info@punkt.de http://www.punkt.de Gf: J=C3=BCrgen Egeling AG Mannheim 108285