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