From nobody Mon Aug 25 09:11:51 2025 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4c9Q7C36LDz65Svm for ; Mon, 25 Aug 2025 09:12:55 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (prime256v1) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "E5" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4c9Q7B5nlSz3sKd; Mon, 25 Aug 2025 09:12:54 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; none List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1756113167; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ETAtV8UpyQm4riKzwkbKCgnpXtkStzA6vdwHjpfG0/k=; b=hR/75S/gFz56mUZbyAi9XFy2Q6oEpZ0C13jTPqrS51CxJmq9bVtRgnfSWITKsaIj9Q4j1y MYNFRAwactz5BjjfxAwIa7EfC1Q/kKzD9D3FUhN2xEyCKL9zOw55pZTFVsd5d+E75eZc/2 kSHAnZY+obgK9RhRsIR0Tc7lHdJ1o+yUaQ1SFrDjijTQaE+j6FVncBnbRTi5TdSOnjWRlS /71oPICrS9isaXbVEjAlm7XozqexFALbG/a1MgfLVJ5B7iUWtyWxwZzt+TZNFCtgifgP56 gw5BBPNY19TAx3wNieMsHRZqUJikQF989RvnmxtnOYBkeRgym9B6xDSGXxpmOw== Date: Mon, 25 Aug 2025 11:11:51 +0200 From: Alexander Leidinger To: Marcin Cieslak Cc: Kyle Evans , Xin LI , Current , Gleb Smirnoff Subject: Re: UPDATING stuff In-Reply-To: <2r579os7-29n7-890r-9210-s3s1n4r0s4qo@fncre.vasb> References: <2r579os7-29n7-890r-9210-s3s1n4r0s4qo@fncre.vasb> Message-ID: <548137ff7d2289fa60a1cba14afa4957@Leidinger.net> Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_f78c7ee47996da30feb57c953522600d"; micalg=pgp-sha256 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4c9Q7B5nlSz3sKd This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_f78c7ee47996da30feb57c953522600d Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Am 2025-08-25 10:44, schrieb Marcin Cieslak: > 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 This is normally documented in https://docs.freebsd.org/en/books/porters-handbook/versions/ (intended to be updated at the time when the FreeBSD_versions is increased), but I can agree that the info there is a bit terse sometimes. > - 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. What do you think about this? diff --git UPDATING UPDATING index ddb2e7603b2a..e197940c6431 100644 --- UPDATING +++ UPDATING @@ -73,6 +73,12 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 15.x IS SLOW: If you only have FreeBSD-sendmail installed for applications that require libmilter, you can now remove it. +20250815: + The [gs}etgroups(2)syscalls have changed. To maintain backwards + compatibility with existing programs, you need COMPAT_FREEBSD14 in + your kernel config until all applications which use this are + rebuild/reinstalled. + 20250815: jemalloc 5.3.0 has been committed to the tree. Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_f78c7ee47996da30feb57c953522600d Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmisKOYACgkQEg2wmwP4 2Ib/zBAAgqPHJL7ipKhOXRq9n7UsD0mAr5i1vc/wHDfaKNocdsSqi/9nHn0NVGBI jZ8jcl0SHvjFqk0Aw7GRfOFU/qdKc1obdjisWGLHv82gJ47oskGOPSarrAoP4idD y//EiBvHOQu9dixiisFS/4s2pzN6TV8gVdqdTRrBVAn0sTf5nDmK1oEjTJWkaGPL MxpeYgdoA+LP0Jo1PBj/csSpIRBvasPrmyVftVtPoAN/NXvOOfBZJXdCIJyZJgbd 856v5IwYXN8ywmfUVwrxGo32i/R03TXGvMLPRV3GZNk13AxvUBDgbCAVexV7nhm8 sJzsicvD+wSHtjJJbccmWy53foW7wiDWpCqoc1IxYa6obeI+nVcmZHqE1vBYNXYq iw7tVOlk1RkdoEb8jBOn787w0UHq1xJvEv+qWBTHhUj3qE36a1p+e80uQr8dxB35 2U/zUnnQpc0r9/oJ+40Dks5lZMeI81YdXLEAE7H/JbHJIfXcO+yKrAsh1+lkO2xv Ig7l5eQXYLb7V+kGbY34Y9/4uDqbSchb5Gp3Nj+s2cIRbUpMS7iZo0w14mmhrs5G 3rubT9vRECWRTZJ2H/9ZLGDflCSeDIINPyJfDRkWlvozN94erdwv1eoCsGHotdpn wD+XrMjtSS2y2wMJlV2a/CDfOH0eh/Evy3kR2wbKfsYqjHjb8RA= =9PZy -----END PGP SIGNATURE----- --=_f78c7ee47996da30feb57c953522600d--