Summary: | (58) FreeBSD 13.1 release notes: draft: UEFI boot etc. | ||||||
---|---|---|---|---|---|---|---|
Product: | Documentation | Reporter: | Graham Perrin <grahamperrin> | ||||
Component: | Website | Assignee: | freebsd-doc (Nobody) <doc> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Many People | CC: | gjb, kib, re | ||||
Priority: | --- | ||||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
URL: | https://github.com/freebsd/freebsd-doc/pull/58 | ||||||
See Also: |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263303 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256746 |
||||||
Attachments: |
|
Description
Graham Perrin
2022-03-02 16:06:59 UTC
<https://www.freebsd.org/releases/13.1R/relnotes/> (draft) If you can add the paragraph below, then I'll wrap up (close) the PR in GitHub. Thanks. ---- UEFI boot is improved for amd64. The loader detects whether the loaded kernel can handle the in-place staging area (non-copying mode). The default is `copy_staging auto`. Auto-detection can be overridden, for example: with `copy_staging enable`, the loader will unconditionally copy the staging area to 2M, regardless of kernel capabilities. Also, the code to grow the staging area is more robust; for growth to occur, it's no longer necessary to hand-tune and recompile the loader. _(Sponsored by the FreeBSD Foundation)_ ---- kib@ that is, paraphrased from the final paragraph of <https://www.freebsd.org/status/report-2021-07-2021-09/#_improved_amd64_uefi_boot>. Please, have I preserved the essence? In particular (original): > … detects if the loaded kernel can handle in-place staging area … – becomes (here): > … detects whether the loaded kernel can handle the in-place staging area … – correct? Created attachment 233652 [details] Screenshot: 13.0 to the left, 13.1 (draft) to the right For 13.0, future tense is wrong; "will change", and so on. > … FreeBSD 13.0 will continue to support older CPUs, … Should that be 13.1? > … This change does not affect … Should that be _did_ not affect? > General Notes Regarding Future FreeBSD Releases – can not be a heading for a past release. Hmm (In reply to Graham Perrin from comment #2) >> General Notes Regarding Future FreeBSD Releases > > – can not be a heading for a past release. Well, it sort of _can_, but Bugzilla doesn't lend itself to what I have in mind. General Storage <https://www.freebsd.org/releases/13.1R/relnotes/#storage-general> Maybe add a subsection: > UFS Changes – with some blurb about this fix, which is probably significant enough to be mentioned: > fsck_ffs: fix background fsck in preen mode Git reference: fb2feceac34cc9c3fb47ba4a7b0ca31637f8fdf0 <https://github.com/freebsd/freebsd-src/commit/fb2feceac34cc9c3fb47ba4a7b0ca31637f8fdf0> | <https://cgit.freebsd.org/src/commit/?h=releng/13.1&id=fb2feceac34cc9c3fb47ba4a7b0ca31637f8fdf0> For the blurb, it might help to portray the behaviour that _preceded_ the fix. Key points from bug 256746 comment 0: * affected 13.0-RELEASE, 13-STABLE and CURRENT * soft updates without soft update journaling Bump! Will it help if I try to learn Phabricator etc. this evening? Or is it too late for these things to be mentioned in release notes? It's not too late, and I have not forgotten about this. :) (In reply to Graham Perrin from comment #1) ⚙ D35211 13.1-RELEASE note: UEFI boot is improved for amd64 <https://reviews.freebsd.org/D35211> (In reply to Graham Perrin from comment #4) ⚙ D35212 13.1-RELEASE note: fsck_ffs: background fsck <https://reviews.freebsd.org/D35212> Committed as part of https://reviews.freebsd.org/D35211 Thank you for the content, and apologies for the delay getting this committed. (In reply to Glen Barber from comment #8) Similarly: thanks, and my apologies for not getting to Phabricator sooner. I have trouble with Git (but not GitHub). <https://github.com/freebsd/freebsd-doc/pull/58> is closed. Re: <https://github.com/freebsd/freebsd-doc/pull/58#pullrequestreview-897875961> I don't see a release note for reimplementation of stack address randomisation. With announcement of 13.1-RELEASE expected today, let's treat this as too late for addition of a note. ---- Other aspects of the pull request – mostly, to make the template less verbose (less repetitive) – might be revisited at a later date :-) |