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