xref: /freebsd-14.2/RELNOTES (revision ea8d7263)
1Release notes for FreeBSD 14.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
13daf917daba9c:
14	One True Awk updated to 2nd Edition with new -csv support and UTF-8
15	support. See https://awk.dev for more details.
16
17b8e137d8d32d:
18	This commit added some statistics collection to the NFS-over-TLS
19	code in the NFS server so that sysadmins can moditor usage.
20	The statistics are available via the kern.rpc.tls.* sysctls.
21
2241582f28ddf7:
23	FreeBSD 15.0 will not include support for 32-bit platforms.
24	However, 64-bit systems will still be able to run older 32-bit
25	binaries.
26
27	Support for executing 32-bit binaries on 64-bit platforms via
28	COMPAT_FREEBSD32 will remain supported for at least the
29	stable/15 and stable/16 branches.
30
31	Support for compiling individual 32-bit applications via
32	`cc -m32` will also be supported for at least the stable/15
33	branch which includes suitable headers in /usr/include and
34	libraries in /usr/lib32.
35
36	Support for 32-bit platforms in ports for 15.0 and later
37	releases is also deprecated, and these future releases may not
38	include binary packages for 32-bit platforms or support for
39	building 32-bit applications from ports.
40
41	stable/14 and earlier branches will retain existing 32-bit
42	kernel and world support.  Ports will retain existing support
43	for building ports and packages for 32-bit systems on stable/14
44	and earlier branches as long as those branches are supported
45	by the ports system.  However, all 32-bit platforms are Tier-2
46	or Tier-3 and support for individual ports should be expected
47	to degrade as upstreams deprecate 32-bit platforms.
48
49	With the current support schedule, stable/14 will be EOLed 5
50	years after the release of 14.0.  The EOL of stable/14 would
51	mark the end of support for 32-bit platforms including source
52	releases, pre-built packages, and support for building
53	applications from ports.  Given an estimated release date of
54	October 2023 for 14.0, support for 32-bit platforms would end
55	in October 2028.
56
57	The project may choose to alter this approach when 15.0 is
58	released by extending some level of 32-bit support for one or
59	more platforms in 15.0 or later.  Users should use the
60	stable/14 branch to migrate off of 32-bit platforms.
61
623cb2f5f369ec:
63	The lua-flavored loader(8) will now interpret .lua files that appear in
64	loader_conf_files as lua, and execute them in a sandbox.  Existing
65	loader environment variables are available as globals in the sandbox,
66	and any global variable set, if not a table value, will be reflected in
67	the loader environment upon successful execution of the configuration
68	file.  Environment variables with names that aren't valid lua names may
69	be accessed as indices of _ENV; e.g., _ENV['net.fibs'].
70
71bdc81eeda05d:
72	nda is now the default nvme device on all platforms. While nda creates
73	nvd links by default so fstab, etc continues to work, configuration
74	should be updated to the new nda devices.
75
76	To restore the old behavior, add hw.nvme.use_nvd=1 to loader.conf or
77	`options NVME_USE_NVD=1` to the kernel config.  To disable the nvd
78	compatibility aliases, add kern.cam.nda.nvd_compat=0 to loader.conf.
79
80bbb2d2ce4220:
81	Change pw (hence bsdinstall) not to move /home to /usr/home.
82	Previously, when creating the path to home directories, pw
83	would move any path in the root directory under /usr, creating
84	a symlink in root.  In particular, the default /home would become
85	/usr/home.  Now /home is at the top level by default.  /usr/home
86	can be used explicitly.
87
883416e102c4e9:
89	Remove TI code from armv7 GENERIC kernel.
90	This code doesn't cope with newer DTS and hasn't in a long time so
91	support for TI armv7 platform (like BeagleBone and Pandaboard) is now
92	removed from GENERIC.
93
94d198b8774d2c:
95	Add a new "fwget" utility.
96	The goal of this utility is to inspect the system for peripherals
97	that needs firmware and install the appropriate packages for them.
98	For now only pci subsystem is supported and only firmwares for Intel
99	and AMD GPUs are known.
100
101896516e54a8c:
102	Add a new "syskrb5" mount option for Kerberized NFSv4.1/4.2 mounts.
103	Without this patch, a Kerberized NFSv4.1/4.2 mount must provide
104	a Kerberos credential for the client at mount time.
105	This patch uses a feature of NFSv4.1/4.2 called SP4_NONE, which
106	allows the state maintenance operations to be performed by any
107	authentication mechanism, so that these operations may be done via
108	AUTH_SYS instead of RPCSEC_GSS (KerberosV).  As such, no Kerberos
109	credential is required at mount time.
110	See mount_nfs(8).
111
112330aa8acdec7,ff2f1f691cdb:
113	Adds support for the SP4_MACH_CRED case for the
114	NFSv4.1/4.2 ExchangeID operation since the Linux
115	NFSv4.1/4.2 client is now using this for Kerberized mounts.
116	This change should only affect Kerberized NFSv4.1/4.2 mounts.
117	The Linux Kerberized NFSv4.1/4.2 mounts currently work without
118	support for this because Linux will fall back to SP4_NONE,
119	but there is no guarantee this fallback will work forever.
120
1217344856e3a6d and many others:
122	Add support so that nfsd(8), nfsuserd(8), mountd(8), gssd(8)
123	and rpc.tlsservd(8) can be run in an appropriately configured
124	vnet prison.  The vnet prison must be on its own file system,
125	have the "allow.nfsd" jail parameter set on it and enforce_statfs
126	cannot be set to "0".  Use of UDP and pNFS server configurations
127	are not permitted.  (ie. The nfsd command line options "-u", "-p"
128	and "-m" are not supported.)
129	See jail(8), nfsd(8) and mountd(8).
130
1312fb4f839f3fc,d89513ed2050,3413ee88c39d,f97a19ecb985,021562c5020d,431d2a81d421:
132	sendmail has been updated to the latest upstream version (8.17.1).
133
1344a30d7bb373c,d670a8f7c596,af01b4722577,4e240e55d818:
135	The growfs(7) script can now add a swap partition at the end of
136	the expansion area, and does so by default if there is no existing
137	swap.  See growfs(7).
138
13986edb11e7491:
140	llvm-objdump is now always installed as objdump.
141
142616f32ea6da7:
143	mta_start_script along with othermta rc.d script has been retired.
144
145a67b925ff3e5:
146	The default mail transport agent is now dma(8) replacing sendmail.
147
14822893e584032:
149	L3 filtering on if_bridge will do surprising things which aren't
150	fail-safe, so net.link.bridge.pfil_member and
151	net.link.bridge.pfil_bridge now default to zero.
152
153f0bc4ed144fc:
154	A new DTrace provider, kinst, is introduced and documented in
155	dtrace_kinst(4).  The provider allows kernel instructions to be traced,
156	similar to the FBT (function boundary tracing) provider except that all
157	instructions may be probed instead of logical entry and return
158	instructions.  The provider is currently amd64-only.
159
1600aa2700123e2:
161	OPIE has been removed from the base system.  If you still wish
162	to use it, install the security/opie port.  Otherwise, make
163	sure to remove or comment out any mention of pam_opie and
164	pam_opieaccess from your PAM policies (etcupdate will normally
165	take care of this for the stock policies).
166
1670eea46fb1f83:
168	Removed telnetd.
169
170981ef32230b2,33721eb991d8:
171	These commits make the use of NFSv4.1/4.2 mounts with the "intr"
172	mount option fairly usable, although not 100% correct, so long as
173	the "nolockd" mount option is used as well.  See the mount_nfs(8)
174	manual page for more information.
175
176b875d4f5ddcb,0685c73cfe88:
177	The NFSv4.1/4.2 client and server will now generate console messages
178	if sessions are broken, suggesting that users check to ensure
179	that the /etc/hostid strings are unique for all NFSv4.1/4.2 clients.
180
181240afd8c1fcc:
182	makefs(8) has ZFS support; it can create a ZFS pool, backed by a
183	single disk vdev, containing one or more datasets populated from
184	the staging directory.
185
18678ee8d1c4cda,f4f56ff43dbd:
187	The in-tree qat(4) driver has been replaced with Intel's QAT driver.
188	The new version provides additional interfaces to the chipset's
189	cryptographic and compression offload functionality.
190
191	This will have no visible change for most users; however, the new
192	driver does not support Atom C2000 chipsets.  To preserve support for
193	those chipsets, the old driver has been renamed to qat_c2xxx and kept
194	in the tree.  Users of qat(4) on C2000 hardware will thus need to
195	ensure that qat_c2xxx(4) is loaded instead of qat(4).
196
197da5b7e90e740,5a8fceb3bd9f,7b0a665d72c0,13ec1e3155c7,318d0db5fe8a,1ae2c59bcf21:
198	Boottrace is a new kernel-userspace interface for capturing trace
199	events during system boot and shutdown. Event annotations are
200	present in:
201
202	- The boot and shutdown paths in the kernel
203	- Some key system utilities (init(8), shutdown(8), reboot(8))
204	- rc(8) scripts (via boottrace(8))
205
206	In contrast to other existing boot-time tracing facilities like TSLOG,
207	Boottrace focuses on the ease of use and is aimed primarily at system
208	administrators.
209
210	It is available in the default GENERIC kernel and can be enabled by
211	toggling a single sysctl(8) variable.
212
213	See boottrace(4) for more details.
214
21505a1d0f5d7ac:
216	Kernel TLS offload now supports receive-side offload of TLS 1.3.
217
21819dc64451179:
219	if_stf now supports 6rd (RFC5969).
220
221c1d255d3ffdb, 3968b47cd974, bd452dcbede6:
222	Add WiFi 6 support to wpa.
223
224ba48d52ca6c8,4ac3d08a9693,2533eca1c2b9:
225	The default bell tone is now 800Hz. It may be set with kbdcontrol
226	again. There's devd integration for people wishing to use their sound
227	cards for the beep.
228
22992b3e07229ba:
230	net.inet.tcp.nolocaltimewait enabled by default.  It prevents
231	creation of timewait entries for TCP connections that were
232	terminated locally.
233
234d410b585b6f0:
235	sh(1) is now the default shell for the root user.
236
237396851c20aeb:
238	libncursesw has been split into libtinfow and libncursesw, linker
239	scripts should make it transparent for consumers. pkg-config files
240	are also now installed to ease ports detecting the ncurses setup from
241	base.
242
243a422084abbda:
244	LLVM's MemorySanitizer can now be used in amd64 kernels.  See the
245	kmsan(9) manual page for more information.
246
24738da497a4dfc:
248	LLVM's AddressSanitizer can now be used in amd64 kernels.  See the
249	kasan(9) manual page for more information.
250
251f39dd6a97844,23f24377b1a9,628bd30ab5a4:
252	One True Awk has been updated to the latest from upstream
253	(20210727). All the FreeBSD patches, but one, have now been
254	either up streamed or discarded.  Notable changes include:
255		o Locale is no longer used for ranges
256		o Various bugs fixed
257		o Better compatibility with gawk and mawk
258
259	The one FreeBSD change, likely to be removed in FreeBSD 14, is that
260	we still allow hex numbers, prefixed with 0x, to be parsed and
261	interpreted as hex numbers while all other awks (including one
262	true awk now) interpret them as 0 in line with awk's historic
263	behavior.
264
265	A second change, less likely to be noticed, is the historic wart
266	if -Ft meaning to use hard tab characters as the field separator
267	is deprecated and will likely be removed in FreeBSD 14.
268
269ee29e6f31111:
270	Commit ee29e6f31111 added a new sysctl called vfs.nfsd.srvmaxio
271	that can be used to increase the maximum I/O size for the NFS
272	server to any power of 2 up to 1Mbyte while the nfsd(8) is not running.
273	The FreeBSD NFS client can now be set to use a 1Mbyte I/O size
274	via the vfs.maxbcachebuf tunable and the Linux NFS client
275	can also do 1Mbyte I/O.
276	kern.ipc.maxsockbuf will need to be increased.  A console
277	message will suggest a setting for it.
278
279d575e81fbcfa:
280	gconcat(8) has added support for appending devices to the device
281	not present at creation time.
282
28376681661be28:
284	Remove support for asymmetric cryptographic operations from
285	the kernel open cryptographic framework (OCF).
286
287a145cf3f73c7:
288	The NFSv4 client now uses the highest minor version of NFSv4
289	supported by the NFSv4 server by default instead of minor version 0,
290	for NFSv4 mounts.
291	The "minorversion" mount option may be used to override this default.
292