14.0 relnotes: additions to date

[• karels]

Summary

Added items:

• information on upgrading boot loader for ZFS
• jail(8) .include directive
• date -z
• sleep(1) units
• OpenSSH and OpenSSL upgrades (slightly premature)
• AWS cloud additions
• vfs.vnode sysctls
• mention audible bell control
• iwlwifi, rtw88 and related WiFi items
• OpenZFS 2.2 and features
• pf/pfsync additions

[• karels]

Adding doc folks. Note that the markup in the first block (boot loader upgrade) needs work.

[carlavilla]

I'll take a look later, btw, thanks for taking care of this!

I'll upgrade the hardware review in a couple hours too

[grahamperrin]

Thanks @karels for the pointer.

https://mastodon.bsd.cafe/@grahamperrin/111239333951787203 tl;dr

1. caution against inappropriate use of gpart(8)
2. out of scope for this review, belatedly add a comparable caution to https://www.freebsd.org/releases/13.2R/relnotes/#boot.

[grahamperrin]

website/content/en/releases/14.0R/relnotes.adoc

58

Non-ASCII characters? (Copied and pasted from something, maybe?)

158

248

272

316

418

Can the version be specified?

For the benefit of people who might read these notes a few weeks, or months, from now.

421

Either specify a version, or drop the vagueness.

423

This sentence might benefit from a comma, or two.

531

Assume that first time readers of these release notes will have no special interest in, or knowledge of, a prerelease period during which a different default (or the sysctl) might have applied.

Block cloning is, essentially, a new feature (compared to 13.2).

For anyone who would like to expand the note a little: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.0 includes the upstream release note about the feature.

535

542

582

584

Should this be a link to the manual page?

[• karels]

Thanks. I'll make the rest of the changes in the next update to the review.

website/content/en/releases/14.0R/relnotes.adoc

58

This was copied and pasted into vi, which shows only spaces. I thought this block should be reformatted in any case, as a block display or something like that. If nothing else, I have typed over this with spaces.

418

I'll inquire; I don't know.

423

I don't see a place where comma is appropriate, but I agree that the sentence is cumbersome.

531

Although block cloning is a new feature, it is optional, and it is relevant that it is enabled by default. (More so to those who watch the mailing lists, but still relevant.)

[• karels]

address most review comments; add mention of audible bell control

[• karels]

zfs bclone is disabled by default; so indicate, and say how to enable.

[emaste]

website/content/en/releases/14.0R/relnotes.adoc

52

This will only be true if the system was installed from a recent enough release, right?

Loader.efi does have "Updating loader.efi on the ESP" under EXAMPLES, but does not mention fstab.

249

We'll want to update this too.
Commit 676824f5cdf9dfdbfca38c9cfff2398345db9211

275

For OpenSSL I think it's fine to reference the main update from 1.1.1 rather than the most recent update that upgraded to 3.0.11. (In contrast to OpenSSH.)

397

PR274502

[imp]

website/content/en/releases/14.0R/relnotes.adoc

52

That is true since 13.0.

58

There's no non ascii characters here. Maybe you mean something else?

[grahamperrin]

website/content/en/releases/14.0R/relnotes.adoc

58

Weirdness was visible in a previous revision:

{F69441344}

If my previous comment was marked Done but then, not shown as such, it might be symptomatic of the Phabricator issue that's listed (with a link out to a screenshot) under https://wiki.freebsd.org/Phabricator#Done. I shouldn't derail this review, so if anyone would like to discuss the issue, please find me in Matrix. Thanks.

[emaste]

website/content/en/releases/14.0R/relnotes.adoc

52

Yeah, but there will certainly be some folks upgrading systems that were first installed with a version prior to 13.0

[grahamperrin]

In D42214#963101, @grahamperrin wrote:

1. caution against inappropriate use of gpart(8)
2. out of scope for this review, belatedly add a comparable caution to https://www.freebsd.org/releases/13.2R/relnotes/#boot.

On second thoughts, better to express these two cautions in a more relevant page:

• FreeBSD 14.0-RELEASE installation information

Not yet visible at https://www.freebsd.org/releases/14.0R/ (and not yet present at https://github.com/freebsd/freebsd-doc/tree/main/website/content/en/releases/14.0R).

website/content/en/releases/14.0R/relnotes.adoc

51

This entire paragraph might be better placed in:

• FreeBSD 14.0-RELEASE installation information

[• karels]

website/content/en/releases/14.0R/relnotes.adoc

52

I have a system that may be that old. efibootmgr -v doesn't show a File on the primary line. I assume that means it uses boot/bootx86.efi; @imp, is that correct? If so, I can clarify this. That system has the ESP in fstab without noauto, so it is always mounted. I'll clarify this. Looks like it will require a little rearrangement though.

58

There were non-ASCII characters, and some bad formatting; I fixed both.

249

I could have sworn I changed this; fixed in my copy now.

531

But it's not enabled by default; fixed.

[• karels]

finish updating OpenSSH info

[• karels]

Mark comments as done where appropriate.

website/content/en/releases/14.0R/relnotes.adoc

397

Is there a way to link to the PR? I haven't seen that.

[imp]

website/content/en/releases/14.0R/relnotes.adoc

52

If the entries are 'generated' by the firmware, they are supposed to have a File element. Older firmwares do really crazy things... Including omitting the File... When that happens, you have to assume the default for removable media, which is \efi\boot\bootXXX.efi... It's often a total crap shoot on these systems.

Also to note: if your ESP is on a gmirror, the firmware will report that it's on one of the mirror underlying devices since the doesn't know about gmirror.

And the (null) will report the full unix path if the ESP is already mounted. When the ESP is mounted, sometimes the matching up code gets things wrong wrt gmirror and other geom constructs...

[emaste]

bhyve improvements were brought up on mastodon, https://mastodon.social/deck/@ronnie_bonkers/111229359750925574
I think much of this is in 13.2 (which we've been discussing as a separate topic) but Michael Dexter mentioned @corvink's TPM passthrough work

[emaste]

from https://mastodon.social/deck/@[e-mail]/111230783694024630
diff(1) --color support f38702e5a52e1350b9349bc297ccd0b50b1941c3

[emaste]

https://ipv6.social/@tuxpowered/111239166771971768
pfsync format changed
@kp might be able to suggest a description

[kp]

In D42214#963330, @emaste wrote:

https://ipv6.social/@tuxpowered/111239166771971768
pfsync format changed
@kp might be able to suggest a description

Possibly something like

The pfsync packet format has been extended to improve support for route-to rules. This format is incompatible with older releases. The old format can be selected using ifconfig pfsync0 version 1301. This is especially important if members of a pfsync cluster are not upgraded simultaneously.

[• karels]

Thanks, Kristof. Is there a git hash to cite for this (or a small number of them)? Any sponsor?

[emaste]

These generally look good to me. I think the UEFI loader instructions could use a little refinement (probably more a handbook and/or man page update than release notes) and we still have the open question for 13.1/13.2. Maybe commit without those bits for now?

website/content/en/releases/14.0R/relnotes.adoc

199

Should we mention that multiple delay values are summed?
Aside, I'm not sure how often that would actually get used but it does allow things like sleep 1m 30s

397

The only thing I've found is (from an errata list), See link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250434[PR 250434] for additional details.

But this PR is for adding to the release notes, so I guess just reference it in the commit message.

418

CC @bz

[vegeta_tuxpowered.net]

In D42214#963332, @kp wrote:

In D42214#963330, @emaste wrote:

https://ipv6.social/@tuxpowered/111239166771971768
pfsync format changed
@kp might be able to suggest a description

Possibly something like

The pfsync packet format has been extended to improve support for route-to rules. This format is incompatible with older releases. The old format can be selected using ifconfig pfsync0 version 1301. This is especially important if members of a pfsync cluster are not upgraded simultaneously.

I'd also mention that more things got fixed with the new packet format:

The pfsync packet format has been extended to improve support for queuing, scrubbing and route-to rules. This format is incompatible with older releases. The old format can be selected using ifconfig pfsync0 version 1301. This is especially important if members of a pfsync cluster are not upgraded simultaneously.

[grahamperrin]

website/content/en/releases/14.0R/relnotes.adoc

62

A mixture of reverse \ and forward / solidi, is this intentional?

[emaste]

website/content/en/releases/14.0R/relnotes.adoc

62

UEFI and the variables use DOS-style \, FreeBSD mount points and paths use /.

[grahamperrin]

website/content/en/releases/14.0R/relnotes.adoc

62

I see:

\EFI\boot/bootXXX.efi

I mean, this mixture in a single phrase:

\\/

Sorry if I'm misunderstanding. Find it difficult to digest in Phabricator.

[• karels]

btw, I'm waiting for input on a few things, and I'm running some experiments with upgrades and the ESP. I will take a crack at reworking the ESP upgrade, in particular finding the partition and mounting it. It may be that at least some of that belongs in the installation page, but I'd like at least a heads-up here. We can sort it out when the install document is done.

website/content/en/releases/14.0R/relnotes.adoc

62

Take a look at the Boot0000 output, it's copied and pasted, and shows the DOS and BSD paths for the same thing (although BSD is usually displayed in lower case).

[imp]

website/content/en/releases/14.0R/relnotes.adoc

62

\EFI\boot/bootXXX.efi
is my mistake. The / should be a \. It's tricky to see...
Good Eye Graham.

[• karels]

fix incorrect slash in ESP; add pfsync compatibility note; touch up date(1)

[grahamperrin]

Approved, thanks.

After https://cgit.freebsd.org/doc/tree/website/content/en/releases/14.0R/installation.adoc is created, with the customary Upgrading FreeBSD content, then thought can be given to foot-shooting (e.g. https://reviews.freebsd.org/D42214#963193).

[• karels]

I took the liberty of pushing 0f5573f88b30 along with this version, with a couple of touchups to this version: rework the section on mounting the ESP to update loader.efi, and info about the iwlwifi chipsets supported from @bz.