Date: Sat, 22 May 2021 01:46:46 +0100 From: Graham Perrin <grahamperrin@gmail.com> To: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: zpool upgrade and bootcode on 13-RELEASE Message-ID: <3940e10d-e258-945e-fe99-4d3544541033@gmail.com> In-Reply-To: <8A7B5F0F-BDF8-4915-8868-0D39C6579110@grem.de> References: <f50e56e0-fae6-9b22-6765-a333fcc88c14@gmail.com> <8A7B5F0F-BDF8-4915-8868-0D39C6579110@grem.de>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. --------------376F4F07C50EC374B5C2EFE7 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit On 20/05/2021 00:13, Michael Gmelin wrote: > >> On 20. May 2021, at 00:18, Graham Perrin <grahamperrin@gmail.com> wrote: >> >> … > > Given that I upgraded the zpool of a server that boots of a legacy > boot partition, how would the red alert box saying > > "Updating UEFI ESP partitions (the partition the firmware boots > from) has changed. SeeBoot Loader Changes > <https://www.freebsd.org/releases/13.0R/relnotes/#boot>for important > details." > > have caught my attention? No UEFI involved at my end, no zpools > involved in the warning (I noticed the absence of the warning after > running "zpool upgrade", so no harm done, but other users might be > less fortunate). > > -m In a lucky situation: a red alert for changes to something other than the freebsd-boot partition might, obliquely, cause the reader to wonder about changes to the freebsd-boot partition that are not classified as changes for release note purposes :-) That's with a smile, no personal criticism intended, because I am <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256024#c8>; amongst the people who misinterpreted part of the release notes. For anyone who's not following that particular bug (for the command, the action of upgrading a pool), there's a parallel bug for the FreeBSD Handbook: 255318 – handbook: Document how to update the bootloader <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255318>; Add <https://man.freebsd.org/zpool-upgrade(8)>; to the mix. Eventually we should have a handbook, a manual page and an action that are reasonably foolproof. Free from fortune, luck, obliqueness and wonder :-) --------------376F4F07C50EC374B5C2EFE7 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <div class="moz-cite-prefix">On 20/05/2021 00:13, Michael Gmelin wrote:<br> </div> <blockquote type="cite" cite="mid:8A7B5F0F-BDF8-4915-8868-0D39C6579110@grem.de"> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> <div dir="ltr"><br> <blockquote type="cite">On 20. May 2021, at 00:18, Graham Perrin <a class="moz-txt-link-rfc2396E" href="mailto:grahamperrin@gmail.com"><grahamperrin@gmail.com></a> wrote:<br> <br> </blockquote> </div> <blockquote type="cite"> <div dir="ltr">…<span></span><br> </div> </blockquote> <br> <div>Given that I upgraded the zpool of a server that boots of a legacy boot partition, how would the red alert box saying</div> <div><br> </div> <div> "<span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); -webkit-text-size-adjust: auto;">Updating UEFI ESP partitions (the partition the firmware boots from) has changed. See</span><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); -webkit-text-size-adjust: auto;"> </span><a href="https://www.freebsd.org/releases/13.0R/relnotes/#boot" style="caret-color: rgb(0, 0, 0); -webkit-text-size-adjust: auto; color: rgb(0, 0, 0);" moz-do-not-send="true">Boot Loader Changes</a><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); -webkit-text-size-adjust: auto;"> </span><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); -webkit-text-size-adjust: auto;">for important details."</span></div> <div><br> </div> <div>have caught my attention? No UEFI involved at my end, no zpools involved in the warning (I noticed the absence of the warning after running "zpool upgrade", so no harm done, but other users might be less fortunate).</div> <div><br> </div> <div>-m</div> </blockquote> <p><br> </p> <p>In a lucky situation: a red alert for changes to something other than the freebsd-boot partition might, obliquely, cause the reader to wonder about changes to the freebsd-boot partition that are not classified as changes for release note purposes :-) <br> </p> <p>That's with a smile, no personal criticism intended, because I am <a class="moz-txt-link-rfc2396E" href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256024#c8"><https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256024#c8></a>; amongst the people who misinterpreted part of the release notes. <br> </p> <p>For anyone who's not following that particular bug (for the command, the action of upgrading a pool), there's a parallel bug for the FreeBSD Handbook: <br> </p> <p>255318 – handbook: Document how to update the bootloader<br> <a class="moz-txt-link-rfc2396E" href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255318"><https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255318></a></p>; <p>Add <a class="moz-txt-link-rfc2396E" href="https://man.freebsd.org/zpool-upgrade(8)"><https://man.freebsd.org/zpool-upgrade(8)></a>; to the mix. <br> </p> <p>Eventually we should have a handbook, a manual page and an action that are reasonably foolproof. Free from fortune, luck, obliqueness and wonder :-)<br> </p> </body> </html> --------------376F4F07C50EC374B5C2EFE7--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3940e10d-e258-945e-fe99-4d3544541033>