Page MenuHomeFreeBSD

relnotes: clarify that snapshots were previously possible without SU+J
ClosedPublic

Authored by emaste on Apr 17 2023, 9:08 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mar 13 2024, 10:34 AM
Unknown Object (File)
Feb 15 2024, 12:30 PM
Unknown Object (File)
Feb 15 2024, 12:29 PM
Unknown Object (File)
Dec 23 2023, 11:15 AM
Unknown Object (File)
Dec 13 2023, 3:51 AM
Unknown Object (File)
Aug 15 2023, 2:35 AM
Unknown Object (File)
Aug 15 2023, 12:59 AM
Unknown Object (File)
Jul 31 2023, 12:04 PM
Subscribers

Details

Summary

Based on misunderstanding in https://forums.theregister.com/forum/all/2023/04/13/freebsd_132_openbsd_73/, make it clear that snapshots w/o SU+J was possible before and that snapshots with SU+J is the new functionality

Diff Detail

Repository
R9 FreeBSD doc repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

emaste created this revision.

I'd be happy if someone can come up with a more concise way to make this clear.

website/content/en/releases/13.2R/relnotes.adoc
330

Possibly s/that did not enable/without/?

For what it's worth, this seemed clear enough to me before, but it can't hurt to be explicit.

update based on karels feedback

website/content/en/releases/13.2R/relnotes.adoc
330

It seemed clear enough to me as well, although of course I had a lot of context.

This revision is now accepted and ready to land.Apr 18 2023, 12:48 AM
This revision now requires review to proceed.Apr 18 2023, 8:08 PM

When I looked at how this rendered my edit seemed out of place -- the "Thus it is..." really belongs with the first sentence. So just make this a parenthetical comment at the end. Also I think "incompatible with" is more clear/less repetitive than "did not enable" or "filesystems without"

I agree, this is better.

This revision is now accepted and ready to land.Apr 18 2023, 9:04 PM

Similarly, in the announcement (the first link in Liam's article):

  • It is now possible to take snapshots on UFS filesystems when running with journaled soft updates.

If you do lean towards an update of the announcement (personally, I don't), maybe put it in the context of draft https://github.com/freebsd/freebsd-doc/pull/166. Thanks

If you do lean towards an update of the announcement [...]

The announcement text should only be updated if there is something glaringly wrong (i.e., wrong FreeBSD version number, or the like). Any other updates to it should go in the errata file instead.