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