Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 25 Aug 2025 08:44:39 +0000
From:      Marcin Cieslak <saper@saper.info>
To:        Alexander Leidinger <Alexander@Leidinger.net>
Cc:        Kyle Evans <kevans@freebsd.org>, Xin LI <delphij@gmail.com>, Current <current@freebsd.org>, Gleb Smirnoff <glebius@freebsd.org>
Subject:   UPDATING stuff
Message-ID:  <2r579os7-29n7-890r-9210-s3s1n4r0s4qo@fncre.vasb>

index | next in thread | raw e-mail

[-- Attachment #1 --]
On Thu, 21 Aug 2025, Alexander Leidinger wrote:

>>> COMPAT_FREEBSD14?  (Recently [gs]etgroups were changed, with compatibility 
>>> syscalls moved to COMPAT_FREEBSD14).
>
> UPDATING only mentions VMM stuff for COMPAT_FREEBSD14. I give this a try 
> tomorrow. But would this also affect the zfs dataset stuff?

This thread could have been a simple UPDATING update.  I think this is the fourth
time or so I have run into problems, because the changes were not explained.

UPDATING entry on VMM got only there after I've spent 2 days+ troubleshooting
my wifibox failures.

When I read your message I was immediately thinking you might need "COMPAT_FREEBSD14",
but, again, I couldn't find any obvious entry neither in the docs nor in
the git log I was looking at.

@glebus - maybe during the stabilization effort the changes done to the tree
could be reviewed and documented?

  - where the FreeBSD_version got bumped and why
  - ABI changes
  - ....

For example it could be useful to be able to find the information "what
does COMPAT_FREEBSD14 do exactly" in the UPDATING/release notes file.
Otherwise I can't be sure if I need that option or "is my system fresh enough"
to remove it from the kernel.

Marcin Cielak
[-- Attachment #2 --]
0v	*H
g0c10
	`He0	*H

00xJѤ&Q<fUC0
	*H
0L1 0UGlobalSign Root CA - R310U

GlobalSign10U
GlobalSign0
200916000000Z
290318000000Z0[10	UBE10U
GlobalSign nv-sa110/U(GlobalSign GCC R3 PersonalSign 1 CA 20200"0
	*H
0
'ŲTNZ2'1
{v`5)*hkwH35
V()6'!
0-Pf@.ORǁI;<kN3ĿI>0;::!MxFT[Jqh_0>61t3.-JpTEW˼C!Fsvw'V*94~cMV)ܨdJqt+؎_a+.O_;µWx^U\j̺o00U0U%0++0U00U6
bv.:jQ0U#0K.E$MPc0z+n0l0-+0!http://ocsp.globalsign.com/rootr30;+0/http://secure.globalsign.com/cacert/root-r3.crt06U/0-0+)'%http://crl.globalsign.com/root-r3.crl0LU E0C0A	+2(0402+&https://www.globalsign.com/repository/0
	*H
YkjvSZ9i%5q@WAu"0;g"z?7xI
fi|<Ikc&H*9E ʼn!B
IUrs$IQ>8n	 r`Mkx`ƪt"״?S9׷F΀Ed
ڎP%7	7i$x)slS}@t~lg촪6W$򊂞r.ܚ}4}NLC^F}im1a000"LayG0
	*H
0[10	UBE10U
GlobalSign nv-sa110/U(GlobalSign GCC R3 PersonalSign 1 CA 20200
230307161109Z
260307161109Z0<10Usaper@saper.info10	*H
	saper@saper.info0"0
	*H
0
0MkMG6T/:1L=H3`#}ĥ԰:iܰ8w<˖:H\^I		9ȼJ,+!MH5NS/_*R׶6mό-){ёцaם&<4OnJE`>׊/n䴕5oD޼,~vfNPÅ2V9;.+V9ZO1]^uxqEWt	:ֆD϶.[QwkPO	`mJNj
5>c-g!je>֗xn[_?kG=uCHe?2^4GܙZ*XGl#fVYڱ_i&"r=g
rwV֗w4й
Il"1
whhC
،.w<hgAIUO0l)%잎@CtDVHM<~{}EJ;imrr]<s00U0+00N+0Bhttp://secure.globalsign.com/cacert/gsgccr3personalsign1ca2020.crt0A+05http://ocsp.globalsign.com/gsgccr3personalsign1ca20200LU E0C0A	+2(0402+&https://www.globalsign.com/repository/0	U00IUB0@0><:8http://crl.globalsign.com/gsgccr3personalsign1ca2020.crl0U0saper@saper.info0U%0++0U#06
bv.:jQ0UݕQˣ KbM8L90
	*H

%(G2qYC%M=ؾ,۵w\0}ci`{ĂVzk,4&["Sek`6G30LuW_ ƒd(қƤ?kv.)Aجth:zz׽vwMy^縷81u"rH9za
8S)r@6QqA((pCtpИf(%\Y$ڥbpM1}0y0k0[10	UBE10U
GlobalSign nv-sa110/U(GlobalSign GCC R3 PersonalSign 1 CA 2020"LayG0
	`He0	*H
	1	*H
0	*H
	1
250825084439Z0/	*H
	1" 9
}_}ʝf{s}ʽZ60y	*H
	1l0j0	`He*0	`He0	`He0
*H
0*H
0
*H
@0+0
*H
(0
	*H
鱲_'KA+
;vtrxV򻀙&ƒ*cj)))\p^oumJq͋A@H:o9	ϑiM3a
BNWΗOO=J6M︀%
P92hhF39=^?mq W-xBϵZj"݈|!60B4QtQxIGtwGHV
߭Z1۪)[&OBy'UhcZ\ni%5;cnӁ\KkV*U8KBp6j,2-@vNC_!HњSQ,Kߥf8LHi
HyX]l)Ǎjeb7;QwR*CȑNQ+ߒ˴4z<]g	<p/
Q^ڦ܂6СSVܼ|ee&e	؍
y:o%يE
home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2r579os7-29n7-890r-9210-s3s1n4r0s4qo>