<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/lib/libc/sys, branch release/14.4.0</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=release%2F14.4.0</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=release%2F14.4.0'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2026-01-01T19:04:30Z</updated>
<entry>
<title>ioctl.2: Mention EACCES</title>
<updated>2026-01-01T19:04:30Z</updated>
<author>
<name>Felix Johnson</name>
<email>fjohnson@felix-johnson.com</email>
</author>
<published>2025-12-29T19:21:26Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=7fa86256aaca948671c38f462e9ef4692799d8fc'/>
<id>urn:sha1:7fa86256aaca948671c38f462e9ef4692799d8fc</id>
<content type='text'>
ioctls can fail with EACCES, see sys/kern/tty.c

PR:			239504
MFC after:		3 days
Reviewed by:		ziaee
Reported by:		Brennan Vincent &lt;brennan@umanwizard.com&gt;
Differential Revision:	https://reviews.freebsd.org/D49072

(cherry picked from commit e2afbc45258f2fa4bdcf126e959ac660e76fc802)
</content>
</entry>
<entry>
<title>chroot.2: Remove fchroot reference</title>
<updated>2025-11-10T19:04:35Z</updated>
<author>
<name>Ed Maste</name>
<email>emaste@FreeBSD.org</email>
</author>
<published>2025-10-24T15:23:58Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=27aaff3c09f2ec058e108faff5ea138ef5fc3c23'/>
<id>urn:sha1:27aaff3c09f2ec058e108faff5ea138ef5fc3c23</id>
<content type='text'>
fchroot does not exist in stable/14.

Sponsored by:	The FreeBSD Foundation
</content>
</entry>
<entry>
<title>mkdir.2: Correct HISTORY</title>
<updated>2025-11-06T21:55:20Z</updated>
<author>
<name>Ken Wong</name>
<email>ken.wong@ho.stna.me</email>
</author>
<published>2025-07-14T17:32:54Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=37989ef996a55bd6ebb4b3daa85ac19dda90d594'/>
<id>urn:sha1:37989ef996a55bd6ebb4b3daa85ac19dda90d594</id>
<content type='text'>
PR:		286064
MFC after:	3 days
Reviewed by:	mckusick

(cherry picked from commit 26069bca2d64a76cfafb92d61d58c90140c1b28f)
</content>
</entry>
<entry>
<title>revoke.2: Remove mention of block special device files</title>
<updated>2025-11-03T12:47:01Z</updated>
<author>
<name>Mateusz Piotrowski</name>
<email>0mp@FreeBSD.org</email>
</author>
<published>2025-10-24T17:17:42Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=05120af690fbae7b6d91b2d2ad856086611ff67e'/>
<id>urn:sha1:05120af690fbae7b6d91b2d2ad856086611ff67e</id>
<content type='text'>
Block devices are a thing of a past in FreeBSD.

Reviewed by:	ziaee
MFC after:	3 days
Differential Revision:	https://reviews.freebsd.org/D53332
</content>
</entry>
<entry>
<title>write.2: explain the atomicity guarantees of the writes</title>
<updated>2025-10-31T14:42:18Z</updated>
<author>
<name>Konstantin Belousov</name>
<email>kib@FreeBSD.org</email>
</author>
<published>2025-10-26T14:57:16Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=c19f161f5f65d61c0152587000eff7cae9492843'/>
<id>urn:sha1:c19f161f5f65d61c0152587000eff7cae9492843</id>
<content type='text'>
(cherry picked from commit 1c8d7bb4cf7a6b19262333b2a9b1dacf3094b938)
</content>
</entry>
<entry>
<title>getrlimitusage.2: Update HISTORY section</title>
<updated>2025-10-27T14:35:20Z</updated>
<author>
<name>Ed Maste</name>
<email>emaste@FreeBSD.org</email>
</author>
<published>2025-10-24T12:10:26Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=82b6cd5ef6547da2e3d18fbbc69393d73322df43'/>
<id>urn:sha1:82b6cd5ef6547da2e3d18fbbc69393d73322df43</id>
<content type='text'>
Add 14.2, as this was cherry-picked prior to release.

Reported by:	Harald Eilertsen
Reviewed by:	kib
Sponsored by:	The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D53320

(cherry picked from commit 2387a51af235e4304c63f95465a569c878f49dcd)
(cherry picked from commit 87795ea45407355de4e36388ed6c02ef70b9241a)
</content>
</entry>
<entry>
<title>getgroups.2: Clarify, mention ascending order, add SECURITY CONSIDERATIONS</title>
<updated>2025-10-10T17:15:58Z</updated>
<author>
<name>Olivier Certner</name>
<email>olce@FreeBSD.org</email>
</author>
<published>2025-08-29T22:43:10Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=67cf21e16faf17caa51a53efd4b2fd004dae6821'/>
<id>urn:sha1:67cf21e16faf17caa51a53efd4b2fd004dae6821</id>
<content type='text'>
Clarify and be more precise about the behavior of getgroups(2), in
particular with respect to 'gidsetlen'.

Prefer a terminology close to POSIX terms, i.e., use "effective groups"
instead of "group access list".

Say that getgroups(2) reports the supplementary groups in strictly
ascending order (and mention this has been the case since FreeBSD 14.3).

Add a new SECURITY CONSIDERATIONS section, in particular contrasting
FreeBSD 15's behavior with the current one.

While here, fix some style.

Reviewed by:    gbe (older version)
Sponsored by:   The FreeBSD Foundation
Differential Revision:  https://reviews.freebsd.org/D52286

(cherry picked from commit 4be38acc826f260e4c7d3ebbb9de534db449782e)

As indicated in the original commit message, the manual page was
specifically modified as stable/14's getgroups(2) still has the old
behavior.

The original commit message above was reworked to reflect the actual
commit content.
</content>
</entry>
<entry>
<title>setgroups.2: Add SECURITY CONSIDERATIONS, rework</title>
<updated>2025-10-10T17:15:58Z</updated>
<author>
<name>Olivier Certner</name>
<email>olce@FreeBSD.org</email>
</author>
<published>2025-08-29T15:10:22Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=7d5b7157e91970c11315d753c48aa6bdcd3aa9a2'/>
<id>urn:sha1:7d5b7157e91970c11315d753c48aa6bdcd3aa9a2</id>
<content type='text'>
Add a new SECURITY CONSIDERATIONS section contrasting the current
behavior with the new one in force starting from FreeBSD 15.

Prefer a terminology referring to POSIX terms, i.e., use "effective
group list" instead of "group access list".

While here, fix some style.

Fixes:          9da2fe96ff2e ("kern: fix setgroups(2) and getgroups(2) to match other platforms")
Sponsored by:   The FreeBSD Foundation
Differential Revision:  https://reviews.freebsd.org/D52284

(cherry picked from commit 6d22cd6b5f8b5604f1fe9e70930b1506f990e31e)

As indicated in the original commit message, the manual page was
specifically modified as stable/14's setgroups(2) still
has the old behavior.

The original commit message above was reworked to reflect the actual
commit content.
</content>
</entry>
<entry>
<title>jail.2: Mention EPERM is returned on open directories</title>
<updated>2025-10-10T17:15:55Z</updated>
<author>
<name>Olivier Certner</name>
<email>olce@FreeBSD.org</email>
</author>
<published>2025-09-01T09:31:23Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=6e888a22743f67d3b130dd0a9b9849bcee160d2f'/>
<id>urn:sha1:6e888a22743f67d3b130dd0a9b9849bcee160d2f</id>
<content type='text'>
The manual page does not directly mention this reason for getting EPERM,
instead referring the reader to chroot(2).  We have had some questions
about it recently, in part due to a bug (fixed), and this case is not an
obvious permission/problem, so let's be more explicit.

PR:             280809
Reviewed by:    jamie
MFC after:      3 days
Sponsored by:   The FreeBSD Foundation
Differential Revision:  https://reviews.freebsd.org/D52319

(cherry picked from commit ef2f36be8fce8cf7a62ce7d33ab1c4a181fac3e2)
</content>
</entry>
<entry>
<title>Bump .Dd for recently changed aio_*(2) manpages</title>
<updated>2025-09-24T04:43:41Z</updated>
<author>
<name>Enji Cooper</name>
<email>ngie@FreeBSD.org</email>
</author>
<published>2025-03-28T02:43:26Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=9f94939b73f56fa7f7e53acbd260cad3cfcf91ef'/>
<id>urn:sha1:9f94939b73f56fa7f7e53acbd260cad3cfcf91ef</id>
<content type='text'>
The ones that were effectively unchanged from
d97e44784bb5a^..e24279e0f9e did not have `.Dd` bumped. Only
the ones that had a net content change between those
revisions.

MFC after:	2 weeks
MFC with:	d97e44784bb5a e24279e0f9e

(cherry picked from commit 1b37af092211f9947d9f089f452232b791b9eafc)
</content>
</entry>
</feed>
