Re: FreeBSD Errata Notice FreeBSD-EN-23:16.openzfs
- Reply: Paul Mather : "Re: FreeBSD Errata Notice FreeBSD-EN-23:16.openzfs"
- Reply: Ed Maste : "Re: FreeBSD Errata Notice FreeBSD-EN-23:16.openzfs"
- Reply: Walter Cramer : "Anomoly from `freebsd-update IDS` in 12.4-RELEASE-p9 - dual entries for /etc/ssh/sshd_config"
- In reply to: Thomas Zander : "Re: FreeBSD Errata Notice FreeBSD-EN-23:16.openzfs"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 03 Dec 2023 00:11:48 UTC
Might I also ask (or say): I find some of the notice and actions confusing, at least in minor ways. I'm mainly only remarking since the subject has been opened. First, "Background" talks about FreeBSD 12 ZFS being based on Illumos ZFS, and 13 and on being based on OpenZFS. I kinda wish the notice would say why it tells me that, because the implication in the text is that both are affected. It would be nice if it said "both are affected" right out in the open. I realize it's implied. Second, it gives workaround of "vfs.zfs.dmu_offset_next_sync sysctl to 0" But on my 12.4 systems there is no such sysctl variable. Third, it says the binary upgrade will result in 12.4-RELEASE-p8. When I do the freebsd-update, the result according to uname is 12.4-RELEASE-p6. Thinking that perhaps I have to do it again, I am told No updates needed to update system to 12.4-RELEASE-p8 and yet uname -a still says 12.4-RELEASE-p6. Somebody might ask if I did a reboot, and yes. (and there's still no vfs.zfs.dum_offset variable) Like I said, all pretty minor except maybe the sysctl variable one. I'm mostly bothered because I'm overly literal and/or anal. I was starting from p1. I hadn't seen anything urging me to step up to a different patch level, hopefully I hadn't overlooked anything. -mm- (long time no post)