Date: Mon, 24 Oct 2016 08:59:17 +0200 From: "Patrick M. Hausen" <hausen@punkt.de> To: Ian Smith <smithi@nimnet.asn.au> Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: boot0cfg on does not set default selection on gmirror device Message-ID: <7273E6C8-9462-4389-95B1-D94A15B5BC15@punkt.de> In-Reply-To: <20161024133403.D6806@sola.nimnet.asn.au> References: <14FD5FE6-6277-4EBE-8EE9-630A735F8BEA@punkt.de> <CANCZdfpMGYeMk6FsXFRmN3nGsO6epUx-SPysTUSXKNd1VhuvEQ@mail.gmail.com> <54B556F6-B834-4B0C-A9A4-90B9AD80A668@punkt.de> <CANCZdfoopmRH-i1pdZUHftx7TLLtXRcDNpYPucifmYUNGHdc4g@mail.gmail.com> <BCB5DD63-9BD0-4B55-811B-AB56A2F57E3A@punkt.de> <20161022140755.S6806@sola.nimnet.asn.au> <AC4A443C-E7CE-4D81-B289-FA48C6444E7A@punkt.de> <20161024133403.D6806@sola.nimnet.asn.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, all, > Am 24.10.2016 um 04:50 schrieb Ian Smith <smithi@nimnet.asn.au>: >=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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7273E6C8-9462-4389-95B1-D94A15B5BC15>