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