xref: /freebsd/RELNOTES (revision af66ffbf69e4013401b2e0a51af689c12b62387d)
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
130e8a36a2ab12:
14	Add a new NFS mount option called "mountport" that may be used
15	to specify the port# for the NFS server's Mount protocol.
16	This permits a NFSv3 mount to be done without running rpcbind(8).
17
18b2f7c53430c3:
19	Kernel TLS is now enabled by default in kernels including KTLS
20	support.  KTLS is included in GENERIC kernels for aarch64,
21	amd64, powerpc64, and powerpc64le.
22
23f57efe95cc25:
24	New mididump(1) utility which dumps MIDI 1.0 events in real time.
25
26ddfc6f84f242:
27	Update unicode to 16.0.0 and CLDR to 45.0.0.
28
29b22be3bbb2de:
30	Basic Cloudinit images no longer generate RSA host keys by default for
31	SSH.
32
33000000000000:
34	RSA host keys for SSH are deprecated and will no longer be generated
35	by default in FreeBSD 16.
36
370aabcd75dbc2:
38	EC2 AMIs no longer generate RSA host keys by default for SSH.  RSA
39	host key generation can be re-enabled by setting sshd_rsa_enable="YES"
40	in /etc/rc.conf if it is necessary to support very old SSH clients.
41
42a1da7dc1cdad:
43	The SO_SPLICE socket option was added.  It allows TCP connections to
44	be spliced together, enabling proxy-like functionality without the
45	need to copy data in and out of user memory.
46
47fc12c191c087:
48	grep(1) no longer follows symbolic links by default for
49	recursive searches.  This matches the documented behavior in
50	the manual page.
51
52e962b37bf0ff:
53	When running bhyve(8) guests with a boot ROM, i.e., bhyveload(8) is not
54	used, bhyve now assumes that the boot ROM will enable PCI BAR decoding.
55	This is incompatible with some boot ROMs, particularly outdated builds
56	of edk2-bhyve.  To restore the old behavior, add
57	"pci.enable_bars='true'" to your bhyve configuration.
58
59	Note in particular that the uefi-edk2-bhyve package has been renamed
60	to edk2-bhyve.
61
6243caa2e805c2:
63	amd64 bhyve(8)'s "lpc.bootrom" and "lpc.bootvars" options are
64	deprecated.  Use the top-level "bootrom" and "bootvars" options
65	instead.
66
67822ca3276345:
68	byacc was updated to 20240109.
69
7021817992b331:
71	ncurses was updated to 6.5.
72
731687d77197c0:
74	Filesystem manual pages have been moved to section four.
75	Please check ports you are maintaining for crossreferences.
76
778aac90f18aef:
78	new MAC/do policy and mdo(1) utility which enables a user to
79	become another user without the requirement of setuid root.
80
817398d1ece5cf:
82	hw.snd.version is removed.
83
84a15f7c96a276,a8089ea5aee5:
85	NVMe over Fabrics controller.  The nvmft(4) kernel module adds
86	a new frontend to the CAM target layer which exports ctl(4)
87	LUNs as NVMe namespaces to remote hosts.  The nvmfd(8) daemon
88	is responsible for accepting incoming connection requests and
89	handing off connected queue pairs to nvmft(4).
90
91a1eda74167b5,1058c12197ab:
92	NVMe over Fabrics host.  New commands added to nvmecontrol(8)
93	to establish connections to remote controllers.  Once
94	connections are established they are handed off to the nvmf(4)
95	kernel module which creates nvmeX devices and exports remote
96	namespaces as nda(4) disks.
97
9825723d66369f:
99	As a side-effect of retiring the unit.* code in sound(4), the
100	hw.snd.maxunit loader(8) tunable is also retired.
101
102eeb04a736cb9:
103	date(1) now supports nanoseconds. For example:
104	`date -Ins` prints "2024-04-22T12:20:28,763742224+02:00" and
105	`date +%N` prints "415050400".
106
1076d5ce2bb6344:
108	The default value of the nfs_reserved_port_only rc.conf(5) setting has
109	changed.  The FreeBSD NFS server now requires the source port of
110	requests to be in the privileged port range (i.e., <= 1023), which
111	generally requires the client to have elevated privileges on their local
112	system.  The previous behavior can be restored by setting
113	nfs_reserved_port_only=NO in rc.conf.
114
115aea973501b19:
116	ktrace(2) will now record detailed information about capability mode
117	violations. The kdump(1) utility has been updated to display such
118	information.
119
120f32a6403d346:
121	One True Awk updated to 2nd Edition. See https://awk.dev for details
122	on the additions. Unicode and CSVs (Comma Separated Values) are now
123	supported.
124
125fe86d923f83f:
126	usbconfig(8) now reads the descriptions of the usb vendor and products
127	from usb.ids when available, similarly to what pciconf(8) does.
128
1294347ef60501f:
130	The powerd(8) utility is now enabled in /etc/rc.conf by default on
131	images for the arm64 Raspberry Pi's (arm64-aarch64-RPI img files).
132	This prevents the CPU clock from running slow all the time.
133
1340b49e504a32d:
135	rc.d/jail now supports the legacy variable jail_${jailname}_zfs_dataset
136	to allow unmaintained jail managers like ezjail to make use of this
137	feature (simply rename jail_${jailname}_zfs_datasets in the ezjail
138	config to jail_${jailname}_zfs_dataset.
139
140e0dfe185cbca:
141	jail(8) now support zfs.dataset to add a list of ZFS datasets to a
142        jail.
143
14461174ad88e33:
145	newsyslog(8) now supports specifying a global compression method directly
146	at the beginning of the newsyslog.conf file, which will make newsyslog(8)
147	to behave like the corresponding option was passed to the newly added
148	'-c' option. For example:
149
150	<compress> none
151
152906748d208d3:
153	newsyslog(8) now accepts a new option, '-c' which overrides all historical
154	compression flags by treating their meaning as "treat the file as compressible"
155	rather than "compress the file with that specific method."
156
157	The following choices are available:
158	 * none: Do not compress, regardless of flag.
159	 * legacy: Historical behavior (J=bzip2, X=xz, Y=zstd, Z=gzip).
160	 * bzip2, xz, zstd, gzip: apply the specified compression method.
161
162	We plan to change the default to 'none' in FreeBSD 15.0.
163
1641a878807006c:
165	This commit added some statistics collection to the NFS-over-TLS
166	code in the NFS server so that sysadmins can moditor usage.
167	The statistics are available via the kern.rpc.tls.* sysctls.
168
1697c5146da1286:
170	Mountd has been modified to use strunvis(3) to decode directory
171	names in exports(5) file(s).  This allows special characters,
172	such as blanks, to be embedded in the directory name(s).
173	"vis -M" may be used to encode such directory name(s).
174
175c5359e2af5ab:
176	bhyve(8) has a new network backend, "slirp", which makes use of the
177	libslirp package to provide a userspace network stack.  This backend
178	makes it possible to access the guest network from the host without
179	requiring any extra network configuration on the host.
180
181bb830e346bd5:
182	Set the IUTF8 flag by default in tty(4).
183
184	128f63cedc14 and 9e589b093857 added proper UTF-8 backspacing handling
185	in the tty(4) driver, which is enabled by setting the new IUTF8 flag
186	through stty(1). Since the default locale is UTF-8, enable IUTF8 by
187	default.
188
189ff01d71e48d4:
190	dialog(1) has been replaced by bsddialog(1)
191
19241582f28ddf7:
193	FreeBSD 15.0 will not include support for 32-bit platforms.
194	However, 64-bit systems will still be able to run older 32-bit
195	binaries.
196
197	Support for executing 32-bit binaries on 64-bit platforms via
198	COMPAT_FREEBSD32 will remain supported for at least the
199	stable/15 and stable/16 branches.
200
201	Support for compiling individual 32-bit applications via
202	`cc -m32` will also be supported for at least the stable/15
203	branch which includes suitable headers in /usr/include and
204	libraries in /usr/lib32.
205
206	Support for 32-bit platforms in ports for 15.0 and later
207	releases is also deprecated, and these future releases may not
208	include binary packages for 32-bit platforms or support for
209	building 32-bit applications from ports.
210
211	stable/14 and earlier branches will retain existing 32-bit
212	kernel and world support.  Ports will retain existing support
213	for building ports and packages for 32-bit systems on stable/14
214	and earlier branches as long as those branches are supported
215	by the ports system.  However, all 32-bit platforms are Tier-2
216	or Tier-3 and support for individual ports should be expected
217	to degrade as upstreams deprecate 32-bit platforms.
218
219	With the current support schedule, stable/14 will be EOLed 5
220	years after the release of 14.0.  The EOL of stable/14 would
221	mark the end of support for 32-bit platforms including source
222	releases, pre-built packages, and support for building
223	applications from ports.  Given an estimated release date of
224	October 2023 for 14.0, support for 32-bit platforms would end
225	in October 2028.
226
227	The project may choose to alter this approach when 15.0 is
228	released by extending some level of 32-bit support for one or
229	more platforms in 15.0 or later.  Users should use the
230	stable/14 branch to migrate off of 32-bit platforms.
231