xref: /freebsd/RELNOTES (revision 3068d706eabe99f930fb01d3cbfd74ff1f0eb5a2)
1Release notes for FreeBSD 15.0.
2
3This file describes new user-visible features, changes and updates relevant to
4users of binary FreeBSD releases.  Each entry should describe the change in no
5more than several sentences and should reference manual pages where an
6interested user can find more information.  Entries should wrap after 80
7columns.  Each entry should begin with one or more commit IDs on one line,
8specified as a comma separated list and/or range, followed by a colon and a
9newline.  Entries should be separated by a newline.
10
11Changes to this file should not be MFCed.
12
13dc5ba6b8b4f0:
14	The WITHOUT_GSSAPI src.conf(5) option has been removed.  The GSSAPI
15	libraries are now always built unless WITHOUT_KERBEROS is set.
16
17c43cad871720:
18	jemalloc 5.3.0 has landed. See contrib/jemalloc/ChangeLog
19	for the long list of changes.
20
21cce64f2e6851:
22	Add support for the NFSv4.2 Clone operation, which uses
23	block cloning to "copy on write" files on an NFS server.
24	This only works for exported ZFS file systems that have
25	block cloning enabled, at this time.
26
2737b2cb5ecb0f:
28	Add support to VOP_COPY_FILE_RANGE() for block cloning.
29	At this time, ZFS is the only local file system that supports
30	this and only if block cloning is enabled.  NFSv4.2 also supports it.
31	See pathconf(2) and copy_file_range(2) for more information.
32
332ec2ba7e232d, df58e8b1506f (openzfs 2957eabbe), f61844833ee8, b1b607bd200f,
34	ee95e4d02dbd:
35	Add Solaris style extended attributes (called named attributes
36	in NFSv4).  At this time, only ZFS when the ZFS property called
37	xattr=dir and NFSv4 support them.  The attributes are presented
38	in a directory as regular files.  See named_attribute(7) for
39	more information.
40
41ef2a572bf6:
42	Inline IPSEC offload infrastructure and driver support for mlx5(4)
43	Nvidia ConnectX-6+ network cards were added.
44
4568ba38dad3:
46	amd64: handling of the %fsbase/%gsbase registers and tls base
47	were reworked, making it more useful for apps that directly
48	manipulate CPU context.
49
5078aaab9f1cf:
51	rtld: added support for -z initfirst
52
53e36f069ecb4, c069ca085b:
54	Reliability of UFS on volumes with more than 2G of inodes is
55	significantly improved.  The underlying issue was the invalid
56	interpretation of the 32bit inode number as signed, which got
57	sign-extended into ino_t.
58
59d390633cf8c:
60	On modern amd64 machines (which have the LA57 CPU feature),
61	FreeBSD is able to utilize more than 4TB of RAM.
62
632bd157bc732a:
64	The readdir_r(3) function is deprecated and may be removed in future
65	releases.  Using it in a program will result in compile-time and
66	link-time warnings.
67
689ba51cce8bbd:
69	bsnmpd(1) no longer supports legacy UDP transport.  Users, that have
70	not updated their /etc/snmpd.config since 12.0-RELEASE or older will
71	need to merge in the new configuration.  In particular, the transport
72	definition shall be changed from begemotSnmpdPortStatus OID to
73	begemotSnmpdTransInetStatus.
74
751349a733cf28:
76	Add a driver supporting a new storage controller interface,
77	Universal Flash Storage Host Controller Interface, supporting
78	version 4.1 and earlier, via ufshci(4).
79
80f1f230439fa4:
81	FreeBSD now implements the inotify(2) family of system calls.
82
8350e733f19b37, 171f66b0c2ca:
84	These commits helped improve utilization of NFSv4.1/4.2
85	delegations.  The changes are only used when the NFSv4
86	mount uses the "nocto" mount option and requires an
87	up-to-date NFSv4.1/4.2 server with delegations enabled.
88	For example: For a FreeBSD kernel build with both src
89	and obj NFSv4 mounted, the total RPC count dropped from
90	5461286 to 945643, with a 20% drop in elapsed time.
91
92c3fc0db3bc50
93	The default value of the sysctl variable
94	net.inet.tcp.nolocaltimewait has changed from 1 to 0. This means
95	that FreeBSD does not skip the TIME_WAIT state anymore for
96	endpoints for which the remote address is local. The new sysctl
97	variable net.inet.tcp.msl_local can be used to control the time
98	these endpoints stay in the TIME_WAIT state. The sysctl variable
99	net.inet.tcp.nolocaltimewait is deprecated and intended to be
100	removed in FreeBSD 16.
101
102cd240957d7ba
103	Making a connection to INADDR_ANY (i.e., using INADDR_ANY as an alias
104	for localhost) is now disabled by default.  This functionality can be
105	re-enabled by setting the net.inet.ip.connect_inaddr_wild sysctl to 1.
106
107b61850c4e6f6
108	The bridge(4) sysctl net.link.bridge.member_ifaddrs now defaults to 0,
109	meaning that interfaces added to a bridge may not have IP addresses
110	assigned.  Refer to bridge(4) for more information.
111
11244e5a0150835, 9a37f1024ceb:
113	A new utility sndctl(8) has been added to concentrate the various
114	interfaces for viewing and manipulating audio device settings (sysctls,
115	/dev/sndstat), into a single utility with a similar control-driven
116	interface to that of mixer(8).
117
11893a94ce731a8:
119	ps(1)'s options '-a' and '-A', when combined with any other one
120	affecting the selection of processes except for '-X' and '-x', would
121	have no effect, in contradiction with the rule that one process is
122	listed as soon as any of the specified options selects it (inclusive
123	OR), which is both mandated by POSIX and arguably a natural expectation.
124	This bug has been fixed.
125
126	As a practical consequence, specifying '-a'/'-A' now causes all
127	processes to be listed regardless of other selection options (except for
128	'-X' and '-x', which still apply).  In particular, to list only
129	processes from specific jails, one must not use '-a' with '-J'.  Option
130	'-J', contrary to its apparent initial intent, never worked as a filter
131	in practice (except by accident with '-a' due to the bug), but instead
132	as any other selection options (e.g., '-U', '-p', '-G', etc.) subject to
133	the "inclusive OR" rule.
134
135995b690d1398:
136	ps(1)'s '-U' option has been changed to select processes by their real
137	user IDs instead of their effective one, in accordance with POSIX and
138	the use case of wanting to list processes launched by some user, which
139	is expected to be more frequent than listing processes having the rights
140	of some user.  This only affects the selection of processes whose real
141	and effective user IDs differ.	After this change, ps(1)'s '-U' flag
142	behaves differently then in other BSDs but identically to that of
143	Linux's procps and illumos.
144
1451aabbb25c9f9:
146	ps(1)'s default list of processes now comes from matching its effective
147	user ID instead of its real user ID with the effective user ID of all
148	processes, in accordance with POSIX.  As ps(1) itself is not installed
149	setuid, this only affects processes having different real and effective
150	user IDs that launch ps(1) processes.
151
152f0600c41e754-de701f9bdbe0, bc201841d139:
153	mac_do(4) is now considered production-ready and its functionality has
154	been considerably extended at the price of breaking credentials
155	transition rules' backwards compatibility.  All that could be specified
156	with old rules can also be with new rules.  Migrating old rules is just
157	a matter of adding "uid=" in front of the target part, substituting
158	commas (",") with semi-colons (";") and colons (":") with greater-than
159	signs (">").  Please consult the mac_do(4) manual page for the new rules
160	grammar.
161
16202d4eeabfd73:
163	hw.snd.maxautovchans has been retired. The commit introduced a
164	hw.snd.vchans_enable sysctl, which along with
165	dev.pcm.X.{play|rec}.vchans, from now on work as tunables to only
166	enable/disable vchans, as opposed to setting their number and/or
167	(de-)allocating vchans. Since these sysctls do not trigger any
168	(de-)allocations anymore, their effect is instantaneous, whereas before
169	we could have frozen the machine (when trying to allocate new vchans)
170	when setting dev.pcm.X.{play|rec}.vchans to a very large value.
171
1727e7f88001d7d:
173	The definition of pf's struct pfr_tstats and struct pfr_astats has
174	changed, breaking ABI compatibility for 32-bit powerpc (including
175	powerpcspe) and armv7. Users of these platforms should ensure kernel
176	and userspace are updated together.
177
1785dc99e9bb985, 08e638c089a, 4009a98fe80:
179	The net.inet.{tcp,udp,raw}.bind_all_fibs tunables have been added.
180	They modify socket behavior such that packets not originating from the
181	same FIB as the socket are ignored.  TCP and UDP sockets belonging to
182	different FIBs may also be bound to the same address.  The default
183	behavior is unmodified.
184
185f87bb5967670, e51036fbf3f8:
186	Support for vinum volumes has been removed.
187
1888ae6247aa966, cf0ede720391d, 205659c43d87bd, 1ccbdf561f417, 4db1b113b151:
189	The layout of NFS file handles for the tarfs, tmpfs, cd9660, and ext2fs
190	file systems has changed.  An NFS server that exports any of these file
191	systems will need its clients to unmount and remount the exports.
192
1931111a44301da:
194	Defer the January 19, 2038 date limit in UFS1 filesystems to
195	February 7, 2106. This affects only UFS1 format filesystems.
196	See the commit message for details.
197
19807cd69e272da:
199	Add a new -a command line option to mountd(8).
200	If this command line option is specified, when
201	a line in exports(5) has the -alldirs export option,
202	the directory must be a server file system mount point.
203
2040e8a36a2ab12:
205	Add a new NFS mount option called "mountport" that may be used
206	to specify the port# for the NFS server's Mount protocol.
207	This permits a NFSv3 mount to be done without running rpcbind(8).
208
209b2f7c53430c3:
210	Kernel TLS is now enabled by default in kernels including KTLS
211	support.  KTLS is included in GENERIC kernels for aarch64,
212	amd64, powerpc64, and powerpc64le.
213
214f57efe95cc25:
215	New mididump(1) utility which dumps MIDI 1.0 events in real time.
216
217ddfc6f84f242:
218	Update unicode to 16.0.0 and CLDR to 45.0.0.
219
220b22be3bbb2de:
221	Basic Cloudinit images no longer generate RSA host keys by default for
222	SSH.
223
224000000000000:
225	RSA host keys for SSH are deprecated and will no longer be generated
226	by default in FreeBSD 16.
227
2280aabcd75dbc2:
229	EC2 AMIs no longer generate RSA host keys by default for SSH.  RSA
230	host key generation can be re-enabled by setting sshd_rsa_enable="YES"
231	in /etc/rc.conf if it is necessary to support very old SSH clients.
232
233a1da7dc1cdad:
234	The SO_SPLICE socket option was added.  It allows TCP connections to
235	be spliced together, enabling proxy-like functionality without the
236	need to copy data in and out of user memory.
237
238fc12c191c087:
239	grep(1) no longer follows symbolic links by default for
240	recursive searches.  This matches the documented behavior in
241	the manual page.
242
243e962b37bf0ff:
244	When running bhyve(8) guests with a boot ROM, i.e., bhyveload(8) is not
245	used, bhyve now assumes that the boot ROM will enable PCI BAR decoding.
246	This is incompatible with some boot ROMs, particularly outdated builds
247	of edk2-bhyve.  To restore the old behavior, add
248	"pci.enable_bars='true'" to your bhyve configuration.
249
250	Note in particular that the uefi-edk2-bhyve package has been renamed
251	to edk2-bhyve.
252
25343caa2e805c2:
254	amd64 bhyve(8)'s "lpc.bootrom" and "lpc.bootvars" options are
255	deprecated.  Use the top-level "bootrom" and "bootvars" options
256	instead.
257
258822ca3276345:
259	byacc was updated to 20240109.
260
26121817992b331:
262	ncurses was updated to 6.5.
263
2641687d77197c0:
265	Filesystem manual pages have been moved to section four.
266	Please check ports you are maintaining for crossreferences.
267
2688aac90f18aef:
269	new MAC/do policy and mdo(1) utility which enables a user to
270	become another user without the requirement of setuid root.
271
2727398d1ece5cf:
273	hw.snd.version is removed.
274
275a15f7c96a276,66b5296f1b29:
276	NVMe over Fabrics controller.  The nvmft(4) kernel module adds
277	a new frontend to the CAM target layer which exports ctl(4)
278	LUNs as NVMe namespaces to remote hosts.  The ctld(8) daemon
279	now supports NVMe controllers in addition to iSCSI targets and
280	is responsible for accepting incoming connection requests and
281	handing off connected queue pairs to nvmft(4).
282
283a1eda74167b5,1058c12197ab:
284	NVMe over Fabrics host.  New commands added to nvmecontrol(8)
285	to establish connections to remote controllers.  Once
286	connections are established they are handed off to the nvmf(4)
287	kernel module which creates nvmeX devices and exports remote
288	namespaces as nda(4) disks.
289
29025723d66369f:
291	As a side-effect of retiring the unit.* code in sound(4), the
292	hw.snd.maxunit loader(8) tunable is also retired.
293
294eeb04a736cb9:
295	date(1) now supports nanoseconds. For example:
296	`date -Ins` prints "2024-04-22T12:20:28,763742224+02:00" and
297	`date +%N` prints "415050400".
298
2996d5ce2bb6344:
300	The default value of the nfs_reserved_port_only rc.conf(5) setting has
301	changed.  The FreeBSD NFS server now requires the source port of
302	requests to be in the privileged port range (i.e., <= 1023), which
303	generally requires the client to have elevated privileges on their local
304	system.  The previous behavior can be restored by setting
305	nfs_reserved_port_only=NO in rc.conf.
306
307aea973501b19:
308	ktrace(2) will now record detailed information about capability mode
309	violations. The kdump(1) utility has been updated to display such
310	information.
311
312f32a6403d346:
313	One True Awk updated to 2nd Edition. See https://awk.dev for details
314	on the additions. Unicode and CSVs (Comma Separated Values) are now
315	supported.
316
317fe86d923f83f:
318	usbconfig(8) now reads the descriptions of the usb vendor and products
319	from usb.ids when available, similarly to what pciconf(8) does.
320
3214347ef60501f:
322	The powerd(8) utility is now enabled in /etc/rc.conf by default on
323	images for the arm64 Raspberry Pi's (arm64-aarch64-RPI img files).
324	This prevents the CPU clock from running slow all the time.
325
3260b49e504a32d:
327	rc.d/jail now supports the legacy variable jail_${jailname}_zfs_dataset
328	to allow unmaintained jail managers like ezjail to make use of this
329	feature (simply rename jail_${jailname}_zfs_datasets in the ezjail
330	config to jail_${jailname}_zfs_dataset.
331
332e0dfe185cbca:
333	jail(8) now support zfs.dataset to add a list of ZFS datasets to a
334        jail.
335
33661174ad88e33:
337	newsyslog(8) now supports specifying a global compression method directly
338	at the beginning of the newsyslog.conf file, which will make newsyslog(8)
339	to behave like the corresponding option was passed to the newly added
340	'-c' option. For example:
341
342	<compress> none
343
344906748d208d3:
345	newsyslog(8) now accepts a new option, '-c' which overrides all historical
346	compression flags by treating their meaning as "treat the file as compressible"
347	rather than "compress the file with that specific method."
348
349	The following choices are available:
350	 * none: Do not compress, regardless of flag.
351	 * legacy: Historical behavior (J=bzip2, X=xz, Y=zstd, Z=gzip).
352	 * bzip2, xz, zstd, gzip: apply the specified compression method.
353
354	We plan to change the default to 'none' in FreeBSD 15.0.
355
3561a878807006c:
357	This commit added some statistics collection to the NFS-over-TLS
358	code in the NFS server so that sysadmins can moditor usage.
359	The statistics are available via the kern.rpc.tls.* sysctls.
360
3617c5146da1286:
362	Mountd has been modified to use strunvis(3) to decode directory
363	names in exports(5) file(s).  This allows special characters,
364	such as blanks, to be embedded in the directory name(s).
365	"vis -M" may be used to encode such directory name(s).
366
367c5359e2af5ab:
368	bhyve(8) has a new network backend, "slirp", which makes use of the
369	libslirp package to provide a userspace network stack.  This backend
370	makes it possible to access the guest network from the host without
371	requiring any extra network configuration on the host.
372
373bb830e346bd5:
374	Set the IUTF8 flag by default in tty(4).
375
376	128f63cedc14 and 9e589b093857 added proper UTF-8 backspacing handling
377	in the tty(4) driver, which is enabled by setting the new IUTF8 flag
378	through stty(1). Since the default locale is UTF-8, enable IUTF8 by
379	default.
380
381ff01d71e48d4:
382	dialog(1) has been replaced by bsddialog(1)
383
38441582f28ddf7:
385	FreeBSD 15.0 will not include support for 32-bit platforms.
386	However, 64-bit systems will still be able to run older 32-bit
387	binaries.
388
389	Support for executing 32-bit binaries on 64-bit platforms via
390	COMPAT_FREEBSD32 will remain supported for at least the
391	stable/15 and stable/16 branches.
392
393	Support for compiling individual 32-bit applications via
394	`cc -m32` will also be supported for at least the stable/15
395	branch which includes suitable headers in /usr/include and
396	libraries in /usr/lib32.
397
398	Support for 32-bit platforms in ports for 15.0 and later
399	releases is also deprecated, and these future releases may not
400	include binary packages for 32-bit platforms or support for
401	building 32-bit applications from ports.
402
403	stable/14 and earlier branches will retain existing 32-bit
404	kernel and world support.  Ports will retain existing support
405	for building ports and packages for 32-bit systems on stable/14
406	and earlier branches as long as those branches are supported
407	by the ports system.  However, all 32-bit platforms are Tier-2
408	or Tier-3 and support for individual ports should be expected
409	to degrade as upstreams deprecate 32-bit platforms.
410
411	With the current support schedule, stable/14 will be EOLed 5
412	years after the release of 14.0.  The EOL of stable/14 would
413	mark the end of support for 32-bit platforms including source
414	releases, pre-built packages, and support for building
415	applications from ports.  Given an estimated release date of
416	October 2023 for 14.0, support for 32-bit platforms would end
417	in October 2028.
418
419	The project may choose to alter this approach when 15.0 is
420	released by extending some level of 32-bit support for one or
421	more platforms in 15.0 or later.  Users should use the
422	stable/14 branch to migrate off of 32-bit platforms.
423