1Release notes for FreeBSD 15.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 13c43cad871720: 14 jemalloc 5.3.0 has landed. See contrib/jemalloc/ChangeLog 15 for the long list of changes. 16 17cce64f2e6851: 18 Add support for the NFSv4.2 Clone operation, which uses 19 block cloning to "copy on write" files on an NFS server. 20 This only works for exported ZFS file systems that have 21 block cloning enabled, at this time. 22 2337b2cb5ecb0f: 24 Add support to VOP_COPY_FILE_RANGE() for block cloning. 25 At this time, ZFS is the only local file system that supports 26 this and only if block cloning is enabled. NFSv4.2 also supports it. 27 See pathconf(2) and copy_file_range(2) for more information. 28 292ec2ba7e232d, df58e8b1506f (openzfs 2957eabbe), f61844833ee8, b1b607bd200f, 30 ee95e4d02dbd: 31 Add Solaris style extended attributes (called named attributes 32 in NFSv4). At this time, only ZFS when the ZFS property called 33 xattr=dir and NFSv4 support them. The attributes are presented 34 in a directory as regular files. See named_attribute(7) for 35 more information. 36 37ef2a572bf6: 38 Inline IPSEC offload infrastructure and driver support for mlx5(4) 39 Nvidia ConnectX-6+ network cards were added. 40 4168ba38dad3: 42 amd64: handling of the %fsbase/%gsbase registers and tls base 43 were reworked, making it more useful for apps that directly 44 manipulate CPU context. 45 4678aaab9f1cf: 47 rtld: added support for -z initfirst 48 49e36f069ecb4, c069ca085b: 50 Reliability of UFS on volumes with more than 2G of inodes is 51 significantly improved. The underlying issue was the invalid 52 interpretation of the 32bit inode number as signed, which got 53 sign-extended into ino_t. 54 55d390633cf8c: 56 On modern amd64 machines (which have the LA57 CPU feature), 57 FreeBSD is able to utilize more than 4TB of RAM. 58 592bd157bc732a: 60 The readdir_r(3) function is deprecated and may be removed in future 61 releases. Using it in a program will result in compile-time and 62 link-time warnings. 63 649ba51cce8bbd: 65 bsnmpd(1) no longer supports legacy UDP transport. Users, that have 66 not updated their /etc/snmpd.config since 12.0-RELEASE or older will 67 need to merge in the new configuration. In particular, the transport 68 definition shall be changed from begemotSnmpdPortStatus OID to 69 begemotSnmpdTransInetStatus. 70 711349a733cf28: 72 Add a driver supporting a new storage controller interface, 73 Universal Flash Storage Host Controller Interface, supporting 74 version 4.1 and earlier, via ufshci(4). 75 76f1f230439fa4: 77 FreeBSD now implements the inotify(2) family of system calls. 78 7950e733f19b37, 171f66b0c2ca: 80 These commits helped improve utilization of NFSv4.1/4.2 81 delegations. The changes are only used when the NFSv4 82 mount uses the "nocto" mount option and requires an 83 up-to-date NFSv4.1/4.2 server with delegations enabled. 84 For example: For a FreeBSD kernel build with both src 85 and obj NFSv4 mounted, the total RPC count dropped from 86 5461286 to 945643, with a 20% drop in elapsed time. 87 88c3fc0db3bc50 89 The default value of the sysctl variable 90 net.inet.tcp.nolocaltimewait has changed from 1 to 0. This means 91 that FreeBSD does not skip the TIME_WAIT state anymore for 92 endpoints for which the remote address is local. The new sysctl 93 variable net.inet.tcp.msl_local can be used to control the time 94 these endpoints stay in the TIME_WAIT state. The sysctl variable 95 net.inet.tcp.nolocaltimewait is deprecated and intended to be 96 removed in FreeBSD 16. 97 98cd240957d7ba 99 Making a connection to INADDR_ANY (i.e., using INADDR_ANY as an alias 100 for localhost) is now disabled by default. This functionality can be 101 re-enabled by setting the net.inet.ip.connect_inaddr_wild sysctl to 1. 102 103b61850c4e6f6 104 The bridge(4) sysctl net.link.bridge.member_ifaddrs now defaults to 0, 105 meaning that interfaces added to a bridge may not have IP addresses 106 assigned. Refer to bridge(4) for more information. 107 10844e5a0150835, 9a37f1024ceb: 109 A new utility sndctl(8) has been added to concentrate the various 110 interfaces for viewing and manipulating audio device settings (sysctls, 111 /dev/sndstat), into a single utility with a similar control-driven 112 interface to that of mixer(8). 113 11493a94ce731a8: 115 ps(1)'s options '-a' and '-A', when combined with any other one 116 affecting the selection of processes except for '-X' and '-x', would 117 have no effect, in contradiction with the rule that one process is 118 listed as soon as any of the specified options selects it (inclusive 119 OR), which is both mandated by POSIX and arguably a natural expectation. 120 This bug has been fixed. 121 122 As a practical consequence, specifying '-a'/'-A' now causes all 123 processes to be listed regardless of other selection options (except for 124 '-X' and '-x', which still apply). In particular, to list only 125 processes from specific jails, one must not use '-a' with '-J'. Option 126 '-J', contrary to its apparent initial intent, never worked as a filter 127 in practice (except by accident with '-a' due to the bug), but instead 128 as any other selection options (e.g., '-U', '-p', '-G', etc.) subject to 129 the "inclusive OR" rule. 130 131995b690d1398: 132 ps(1)'s '-U' option has been changed to select processes by their real 133 user IDs instead of their effective one, in accordance with POSIX and 134 the use case of wanting to list processes launched by some user, which 135 is expected to be more frequent than listing processes having the rights 136 of some user. This only affects the selection of processes whose real 137 and effective user IDs differ. After this change, ps(1)'s '-U' flag 138 behaves differently then in other BSDs but identically to that of 139 Linux's procps and illumos. 140 1411aabbb25c9f9: 142 ps(1)'s default list of processes now comes from matching its effective 143 user ID instead of its real user ID with the effective user ID of all 144 processes, in accordance with POSIX. As ps(1) itself is not installed 145 setuid, this only affects processes having different real and effective 146 user IDs that launch ps(1) processes. 147 148f0600c41e754-de701f9bdbe0, bc201841d139: 149 mac_do(4) is now considered production-ready and its functionality has 150 been considerably extended at the price of breaking credentials 151 transition rules' backwards compatibility. All that could be specified 152 with old rules can also be with new rules. Migrating old rules is just 153 a matter of adding "uid=" in front of the target part, substituting 154 commas (",") with semi-colons (";") and colons (":") with greater-than 155 signs (">"). Please consult the mac_do(4) manual page for the new rules 156 grammar. 157 15802d4eeabfd73: 159 hw.snd.maxautovchans has been retired. The commit introduced a 160 hw.snd.vchans_enable sysctl, which along with 161 dev.pcm.X.{play|rec}.vchans, from now on work as tunables to only 162 enable/disable vchans, as opposed to setting their number and/or 163 (de-)allocating vchans. Since these sysctls do not trigger any 164 (de-)allocations anymore, their effect is instantaneous, whereas before 165 we could have frozen the machine (when trying to allocate new vchans) 166 when setting dev.pcm.X.{play|rec}.vchans to a very large value. 167 1687e7f88001d7d: 169 The definition of pf's struct pfr_tstats and struct pfr_astats has 170 changed, breaking ABI compatibility for 32-bit powerpc (including 171 powerpcspe) and armv7. Users of these platforms should ensure kernel 172 and userspace are updated together. 173 1745dc99e9bb985, 08e638c089a, 4009a98fe80: 175 The net.inet.{tcp,udp,raw}.bind_all_fibs tunables have been added. 176 They modify socket behavior such that packets not originating from the 177 same FIB as the socket are ignored. TCP and UDP sockets belonging to 178 different FIBs may also be bound to the same address. The default 179 behavior is unmodified. 180 181f87bb5967670, e51036fbf3f8: 182 Support for vinum volumes has been removed. 183 1848ae6247aa966, cf0ede720391d, 205659c43d87bd, 1ccbdf561f417, 4db1b113b151: 185 The layout of NFS file handles for the tarfs, tmpfs, cd9660, and ext2fs 186 file systems has changed. An NFS server that exports any of these file 187 systems will need its clients to unmount and remount the exports. 188 1891111a44301da: 190 Defer the January 19, 2038 date limit in UFS1 filesystems to 191 February 7, 2106. This affects only UFS1 format filesystems. 192 See the commit message for details. 193 19407cd69e272da: 195 Add a new -a command line option to mountd(8). 196 If this command line option is specified, when 197 a line in exports(5) has the -alldirs export option, 198 the directory must be a server file system mount point. 199 2000e8a36a2ab12: 201 Add a new NFS mount option called "mountport" that may be used 202 to specify the port# for the NFS server's Mount protocol. 203 This permits a NFSv3 mount to be done without running rpcbind(8). 204 205b2f7c53430c3: 206 Kernel TLS is now enabled by default in kernels including KTLS 207 support. KTLS is included in GENERIC kernels for aarch64, 208 amd64, powerpc64, and powerpc64le. 209 210f57efe95cc25: 211 New mididump(1) utility which dumps MIDI 1.0 events in real time. 212 213ddfc6f84f242: 214 Update unicode to 16.0.0 and CLDR to 45.0.0. 215 216b22be3bbb2de: 217 Basic Cloudinit images no longer generate RSA host keys by default for 218 SSH. 219 220000000000000: 221 RSA host keys for SSH are deprecated and will no longer be generated 222 by default in FreeBSD 16. 223 2240aabcd75dbc2: 225 EC2 AMIs no longer generate RSA host keys by default for SSH. RSA 226 host key generation can be re-enabled by setting sshd_rsa_enable="YES" 227 in /etc/rc.conf if it is necessary to support very old SSH clients. 228 229a1da7dc1cdad: 230 The SO_SPLICE socket option was added. It allows TCP connections to 231 be spliced together, enabling proxy-like functionality without the 232 need to copy data in and out of user memory. 233 234fc12c191c087: 235 grep(1) no longer follows symbolic links by default for 236 recursive searches. This matches the documented behavior in 237 the manual page. 238 239e962b37bf0ff: 240 When running bhyve(8) guests with a boot ROM, i.e., bhyveload(8) is not 241 used, bhyve now assumes that the boot ROM will enable PCI BAR decoding. 242 This is incompatible with some boot ROMs, particularly outdated builds 243 of edk2-bhyve. To restore the old behavior, add 244 "pci.enable_bars='true'" to your bhyve configuration. 245 246 Note in particular that the uefi-edk2-bhyve package has been renamed 247 to edk2-bhyve. 248 24943caa2e805c2: 250 amd64 bhyve(8)'s "lpc.bootrom" and "lpc.bootvars" options are 251 deprecated. Use the top-level "bootrom" and "bootvars" options 252 instead. 253 254822ca3276345: 255 byacc was updated to 20240109. 256 25721817992b331: 258 ncurses was updated to 6.5. 259 2601687d77197c0: 261 Filesystem manual pages have been moved to section four. 262 Please check ports you are maintaining for crossreferences. 263 2648aac90f18aef: 265 new MAC/do policy and mdo(1) utility which enables a user to 266 become another user without the requirement of setuid root. 267 2687398d1ece5cf: 269 hw.snd.version is removed. 270 271a15f7c96a276,66b5296f1b29: 272 NVMe over Fabrics controller. The nvmft(4) kernel module adds 273 a new frontend to the CAM target layer which exports ctl(4) 274 LUNs as NVMe namespaces to remote hosts. The ctld(8) daemon 275 now supports NVMe controllers in addition to iSCSI targets and 276 is responsible for accepting incoming connection requests and 277 handing off connected queue pairs to nvmft(4). 278 279a1eda74167b5,1058c12197ab: 280 NVMe over Fabrics host. New commands added to nvmecontrol(8) 281 to establish connections to remote controllers. Once 282 connections are established they are handed off to the nvmf(4) 283 kernel module which creates nvmeX devices and exports remote 284 namespaces as nda(4) disks. 285 28625723d66369f: 287 As a side-effect of retiring the unit.* code in sound(4), the 288 hw.snd.maxunit loader(8) tunable is also retired. 289 290eeb04a736cb9: 291 date(1) now supports nanoseconds. For example: 292 `date -Ins` prints "2024-04-22T12:20:28,763742224+02:00" and 293 `date +%N` prints "415050400". 294 2956d5ce2bb6344: 296 The default value of the nfs_reserved_port_only rc.conf(5) setting has 297 changed. The FreeBSD NFS server now requires the source port of 298 requests to be in the privileged port range (i.e., <= 1023), which 299 generally requires the client to have elevated privileges on their local 300 system. The previous behavior can be restored by setting 301 nfs_reserved_port_only=NO in rc.conf. 302 303aea973501b19: 304 ktrace(2) will now record detailed information about capability mode 305 violations. The kdump(1) utility has been updated to display such 306 information. 307 308f32a6403d346: 309 One True Awk updated to 2nd Edition. See https://awk.dev for details 310 on the additions. Unicode and CSVs (Comma Separated Values) are now 311 supported. 312 313fe86d923f83f: 314 usbconfig(8) now reads the descriptions of the usb vendor and products 315 from usb.ids when available, similarly to what pciconf(8) does. 316 3174347ef60501f: 318 The powerd(8) utility is now enabled in /etc/rc.conf by default on 319 images for the arm64 Raspberry Pi's (arm64-aarch64-RPI img files). 320 This prevents the CPU clock from running slow all the time. 321 3220b49e504a32d: 323 rc.d/jail now supports the legacy variable jail_${jailname}_zfs_dataset 324 to allow unmaintained jail managers like ezjail to make use of this 325 feature (simply rename jail_${jailname}_zfs_datasets in the ezjail 326 config to jail_${jailname}_zfs_dataset. 327 328e0dfe185cbca: 329 jail(8) now support zfs.dataset to add a list of ZFS datasets to a 330 jail. 331 33261174ad88e33: 333 newsyslog(8) now supports specifying a global compression method directly 334 at the beginning of the newsyslog.conf file, which will make newsyslog(8) 335 to behave like the corresponding option was passed to the newly added 336 '-c' option. For example: 337 338 <compress> none 339 340906748d208d3: 341 newsyslog(8) now accepts a new option, '-c' which overrides all historical 342 compression flags by treating their meaning as "treat the file as compressible" 343 rather than "compress the file with that specific method." 344 345 The following choices are available: 346 * none: Do not compress, regardless of flag. 347 * legacy: Historical behavior (J=bzip2, X=xz, Y=zstd, Z=gzip). 348 * bzip2, xz, zstd, gzip: apply the specified compression method. 349 350 We plan to change the default to 'none' in FreeBSD 15.0. 351 3521a878807006c: 353 This commit added some statistics collection to the NFS-over-TLS 354 code in the NFS server so that sysadmins can moditor usage. 355 The statistics are available via the kern.rpc.tls.* sysctls. 356 3577c5146da1286: 358 Mountd has been modified to use strunvis(3) to decode directory 359 names in exports(5) file(s). This allows special characters, 360 such as blanks, to be embedded in the directory name(s). 361 "vis -M" may be used to encode such directory name(s). 362 363c5359e2af5ab: 364 bhyve(8) has a new network backend, "slirp", which makes use of the 365 libslirp package to provide a userspace network stack. This backend 366 makes it possible to access the guest network from the host without 367 requiring any extra network configuration on the host. 368 369bb830e346bd5: 370 Set the IUTF8 flag by default in tty(4). 371 372 128f63cedc14 and 9e589b093857 added proper UTF-8 backspacing handling 373 in the tty(4) driver, which is enabled by setting the new IUTF8 flag 374 through stty(1). Since the default locale is UTF-8, enable IUTF8 by 375 default. 376 377ff01d71e48d4: 378 dialog(1) has been replaced by bsddialog(1) 379 38041582f28ddf7: 381 FreeBSD 15.0 will not include support for 32-bit platforms. 382 However, 64-bit systems will still be able to run older 32-bit 383 binaries. 384 385 Support for executing 32-bit binaries on 64-bit platforms via 386 COMPAT_FREEBSD32 will remain supported for at least the 387 stable/15 and stable/16 branches. 388 389 Support for compiling individual 32-bit applications via 390 `cc -m32` will also be supported for at least the stable/15 391 branch which includes suitable headers in /usr/include and 392 libraries in /usr/lib32. 393 394 Support for 32-bit platforms in ports for 15.0 and later 395 releases is also deprecated, and these future releases may not 396 include binary packages for 32-bit platforms or support for 397 building 32-bit applications from ports. 398 399 stable/14 and earlier branches will retain existing 32-bit 400 kernel and world support. Ports will retain existing support 401 for building ports and packages for 32-bit systems on stable/14 402 and earlier branches as long as those branches are supported 403 by the ports system. However, all 32-bit platforms are Tier-2 404 or Tier-3 and support for individual ports should be expected 405 to degrade as upstreams deprecate 32-bit platforms. 406 407 With the current support schedule, stable/14 will be EOLed 5 408 years after the release of 14.0. The EOL of stable/14 would 409 mark the end of support for 32-bit platforms including source 410 releases, pre-built packages, and support for building 411 applications from ports. Given an estimated release date of 412 October 2023 for 14.0, support for 32-bit platforms would end 413 in October 2028. 414 415 The project may choose to alter this approach when 15.0 is 416 released by extending some level of 32-bit support for one or 417 more platforms in 15.0 or later. Users should use the 418 stable/14 branch to migrate off of 32-bit platforms. 419