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 88cd240957d7ba 89 Making a connection to INADDR_ANY (i.e., using INADDR_ANY as an alias 90 for localhost) is now disabled by default. This functionality can be 91 re-enabled by setting the net.inet.ip.connect_inaddr_wild sysctl to 1. 92 93b61850c4e6f6 94 The bridge(4) sysctl net.link.bridge.member_ifaddrs now defaults to 0, 95 meaning that interfaces added to a bridge may not have IP addresses 96 assigned. Refer to bridge(4) for more information. 97 9844e5a0150835, 9a37f1024ceb: 99 A new utility sndctl(8) has been added to concentrate the various 100 interfaces for viewing and manipulating audio device settings (sysctls, 101 /dev/sndstat), into a single utility with a similar control-driven 102 interface to that of mixer(8). 103 10493a94ce731a8: 105 ps(1)'s options '-a' and '-A', when combined with any other one 106 affecting the selection of processes except for '-X' and '-x', would 107 have no effect, in contradiction with the rule that one process is 108 listed as soon as any of the specified options selects it (inclusive 109 OR), which is both mandated by POSIX and arguably a natural expectation. 110 This bug has been fixed. 111 112 As a practical consequence, specifying '-a'/'-A' now causes all 113 processes to be listed regardless of other selection options (except for 114 '-X' and '-x', which still apply). In particular, to list only 115 processes from specific jails, one must not use '-a' with '-J'. Option 116 '-J', contrary to its apparent initial intent, never worked as a filter 117 in practice (except by accident with '-a' due to the bug), but instead 118 as any other selection options (e.g., '-U', '-p', '-G', etc.) subject to 119 the "inclusive OR" rule. 120 121995b690d1398: 122 ps(1)'s '-U' option has been changed to select processes by their real 123 user IDs instead of their effective one, in accordance with POSIX and 124 the use case of wanting to list processes launched by some user, which 125 is expected to be more frequent than listing processes having the rights 126 of some user. This only affects the selection of processes whose real 127 and effective user IDs differ. After this change, ps(1)'s '-U' flag 128 behaves differently then in other BSDs but identically to that of 129 Linux's procps and illumos. 130 1311aabbb25c9f9: 132 ps(1)'s default list of processes now comes from matching its effective 133 user ID instead of its real user ID with the effective user ID of all 134 processes, in accordance with POSIX. As ps(1) itself is not installed 135 setuid, this only affects processes having different real and effective 136 user IDs that launch ps(1) processes. 137 138f0600c41e754-de701f9bdbe0, bc201841d139: 139 mac_do(4) is now considered production-ready and its functionality has 140 been considerably extended at the price of breaking credentials 141 transition rules' backwards compatibility. All that could be specified 142 with old rules can also be with new rules. Migrating old rules is just 143 a matter of adding "uid=" in front of the target part, substituting 144 commas (",") with semi-colons (";") and colons (":") with greater-than 145 signs (">"). Please consult the mac_do(4) manual page for the new rules 146 grammar. 147 14802d4eeabfd73: 149 hw.snd.maxautovchans has been retired. The commit introduced a 150 hw.snd.vchans_enable sysctl, which along with 151 dev.pcm.X.{play|rec}.vchans, from now on work as tunables to only 152 enable/disable vchans, as opposed to setting their number and/or 153 (de-)allocating vchans. Since these sysctls do not trigger any 154 (de-)allocations anymore, their effect is instantaneous, whereas before 155 we could have frozen the machine (when trying to allocate new vchans) 156 when setting dev.pcm.X.{play|rec}.vchans to a very large value. 157 1587e7f88001d7d: 159 The definition of pf's struct pfr_tstats and struct pfr_astats has 160 changed, breaking ABI compatibility for 32-bit powerpc (including 161 powerpcspe) and armv7. Users of these platforms should ensure kernel 162 and userspace are updated together. 163 1645dc99e9bb985, 08e638c089a, 4009a98fe80: 165 The net.inet.{tcp,udp,raw}.bind_all_fibs tunables have been added. 166 They modify socket behavior such that packets not originating from the 167 same FIB as the socket are ignored. TCP and UDP sockets belonging to 168 different FIBs may also be bound to the same address. The default 169 behavior is unmodified. 170 171f87bb5967670, e51036fbf3f8: 172 Support for vinum volumes has been removed. 173 1748ae6247aa966, cf0ede720391d, 205659c43d87bd, 1ccbdf561f417, 4db1b113b151: 175 The layout of NFS file handles for the tarfs, tmpfs, cd9660, and ext2fs 176 file systems has changed. An NFS server that exports any of these file 177 systems will need its clients to unmount and remount the exports. 178 1791111a44301da: 180 Defer the January 19, 2038 date limit in UFS1 filesystems to 181 February 7, 2106. This affects only UFS1 format filesystems. 182 See the commit message for details. 183 18407cd69e272da: 185 Add a new -a command line option to mountd(8). 186 If this command line option is specified, when 187 a line in exports(5) has the -alldirs export option, 188 the directory must be a server file system mount point. 189 1900e8a36a2ab12: 191 Add a new NFS mount option called "mountport" that may be used 192 to specify the port# for the NFS server's Mount protocol. 193 This permits a NFSv3 mount to be done without running rpcbind(8). 194 195b2f7c53430c3: 196 Kernel TLS is now enabled by default in kernels including KTLS 197 support. KTLS is included in GENERIC kernels for aarch64, 198 amd64, powerpc64, and powerpc64le. 199 200f57efe95cc25: 201 New mididump(1) utility which dumps MIDI 1.0 events in real time. 202 203ddfc6f84f242: 204 Update unicode to 16.0.0 and CLDR to 45.0.0. 205 206b22be3bbb2de: 207 Basic Cloudinit images no longer generate RSA host keys by default for 208 SSH. 209 210000000000000: 211 RSA host keys for SSH are deprecated and will no longer be generated 212 by default in FreeBSD 16. 213 2140aabcd75dbc2: 215 EC2 AMIs no longer generate RSA host keys by default for SSH. RSA 216 host key generation can be re-enabled by setting sshd_rsa_enable="YES" 217 in /etc/rc.conf if it is necessary to support very old SSH clients. 218 219a1da7dc1cdad: 220 The SO_SPLICE socket option was added. It allows TCP connections to 221 be spliced together, enabling proxy-like functionality without the 222 need to copy data in and out of user memory. 223 224fc12c191c087: 225 grep(1) no longer follows symbolic links by default for 226 recursive searches. This matches the documented behavior in 227 the manual page. 228 229e962b37bf0ff: 230 When running bhyve(8) guests with a boot ROM, i.e., bhyveload(8) is not 231 used, bhyve now assumes that the boot ROM will enable PCI BAR decoding. 232 This is incompatible with some boot ROMs, particularly outdated builds 233 of edk2-bhyve. To restore the old behavior, add 234 "pci.enable_bars='true'" to your bhyve configuration. 235 236 Note in particular that the uefi-edk2-bhyve package has been renamed 237 to edk2-bhyve. 238 23943caa2e805c2: 240 amd64 bhyve(8)'s "lpc.bootrom" and "lpc.bootvars" options are 241 deprecated. Use the top-level "bootrom" and "bootvars" options 242 instead. 243 244822ca3276345: 245 byacc was updated to 20240109. 246 24721817992b331: 248 ncurses was updated to 6.5. 249 2501687d77197c0: 251 Filesystem manual pages have been moved to section four. 252 Please check ports you are maintaining for crossreferences. 253 2548aac90f18aef: 255 new MAC/do policy and mdo(1) utility which enables a user to 256 become another user without the requirement of setuid root. 257 2587398d1ece5cf: 259 hw.snd.version is removed. 260 261a15f7c96a276,66b5296f1b29: 262 NVMe over Fabrics controller. The nvmft(4) kernel module adds 263 a new frontend to the CAM target layer which exports ctl(4) 264 LUNs as NVMe namespaces to remote hosts. The ctld(8) daemon 265 now supports NVMe controllers in addition to iSCSI targets and 266 is responsible for accepting incoming connection requests and 267 handing off connected queue pairs to nvmft(4). 268 269a1eda74167b5,1058c12197ab: 270 NVMe over Fabrics host. New commands added to nvmecontrol(8) 271 to establish connections to remote controllers. Once 272 connections are established they are handed off to the nvmf(4) 273 kernel module which creates nvmeX devices and exports remote 274 namespaces as nda(4) disks. 275 27625723d66369f: 277 As a side-effect of retiring the unit.* code in sound(4), the 278 hw.snd.maxunit loader(8) tunable is also retired. 279 280eeb04a736cb9: 281 date(1) now supports nanoseconds. For example: 282 `date -Ins` prints "2024-04-22T12:20:28,763742224+02:00" and 283 `date +%N` prints "415050400". 284 2856d5ce2bb6344: 286 The default value of the nfs_reserved_port_only rc.conf(5) setting has 287 changed. The FreeBSD NFS server now requires the source port of 288 requests to be in the privileged port range (i.e., <= 1023), which 289 generally requires the client to have elevated privileges on their local 290 system. The previous behavior can be restored by setting 291 nfs_reserved_port_only=NO in rc.conf. 292 293aea973501b19: 294 ktrace(2) will now record detailed information about capability mode 295 violations. The kdump(1) utility has been updated to display such 296 information. 297 298f32a6403d346: 299 One True Awk updated to 2nd Edition. See https://awk.dev for details 300 on the additions. Unicode and CSVs (Comma Separated Values) are now 301 supported. 302 303fe86d923f83f: 304 usbconfig(8) now reads the descriptions of the usb vendor and products 305 from usb.ids when available, similarly to what pciconf(8) does. 306 3074347ef60501f: 308 The powerd(8) utility is now enabled in /etc/rc.conf by default on 309 images for the arm64 Raspberry Pi's (arm64-aarch64-RPI img files). 310 This prevents the CPU clock from running slow all the time. 311 3120b49e504a32d: 313 rc.d/jail now supports the legacy variable jail_${jailname}_zfs_dataset 314 to allow unmaintained jail managers like ezjail to make use of this 315 feature (simply rename jail_${jailname}_zfs_datasets in the ezjail 316 config to jail_${jailname}_zfs_dataset. 317 318e0dfe185cbca: 319 jail(8) now support zfs.dataset to add a list of ZFS datasets to a 320 jail. 321 32261174ad88e33: 323 newsyslog(8) now supports specifying a global compression method directly 324 at the beginning of the newsyslog.conf file, which will make newsyslog(8) 325 to behave like the corresponding option was passed to the newly added 326 '-c' option. For example: 327 328 <compress> none 329 330906748d208d3: 331 newsyslog(8) now accepts a new option, '-c' which overrides all historical 332 compression flags by treating their meaning as "treat the file as compressible" 333 rather than "compress the file with that specific method." 334 335 The following choices are available: 336 * none: Do not compress, regardless of flag. 337 * legacy: Historical behavior (J=bzip2, X=xz, Y=zstd, Z=gzip). 338 * bzip2, xz, zstd, gzip: apply the specified compression method. 339 340 We plan to change the default to 'none' in FreeBSD 15.0. 341 3421a878807006c: 343 This commit added some statistics collection to the NFS-over-TLS 344 code in the NFS server so that sysadmins can moditor usage. 345 The statistics are available via the kern.rpc.tls.* sysctls. 346 3477c5146da1286: 348 Mountd has been modified to use strunvis(3) to decode directory 349 names in exports(5) file(s). This allows special characters, 350 such as blanks, to be embedded in the directory name(s). 351 "vis -M" may be used to encode such directory name(s). 352 353c5359e2af5ab: 354 bhyve(8) has a new network backend, "slirp", which makes use of the 355 libslirp package to provide a userspace network stack. This backend 356 makes it possible to access the guest network from the host without 357 requiring any extra network configuration on the host. 358 359bb830e346bd5: 360 Set the IUTF8 flag by default in tty(4). 361 362 128f63cedc14 and 9e589b093857 added proper UTF-8 backspacing handling 363 in the tty(4) driver, which is enabled by setting the new IUTF8 flag 364 through stty(1). Since the default locale is UTF-8, enable IUTF8 by 365 default. 366 367ff01d71e48d4: 368 dialog(1) has been replaced by bsddialog(1) 369 37041582f28ddf7: 371 FreeBSD 15.0 will not include support for 32-bit platforms. 372 However, 64-bit systems will still be able to run older 32-bit 373 binaries. 374 375 Support for executing 32-bit binaries on 64-bit platforms via 376 COMPAT_FREEBSD32 will remain supported for at least the 377 stable/15 and stable/16 branches. 378 379 Support for compiling individual 32-bit applications via 380 `cc -m32` will also be supported for at least the stable/15 381 branch which includes suitable headers in /usr/include and 382 libraries in /usr/lib32. 383 384 Support for 32-bit platforms in ports for 15.0 and later 385 releases is also deprecated, and these future releases may not 386 include binary packages for 32-bit platforms or support for 387 building 32-bit applications from ports. 388 389 stable/14 and earlier branches will retain existing 32-bit 390 kernel and world support. Ports will retain existing support 391 for building ports and packages for 32-bit systems on stable/14 392 and earlier branches as long as those branches are supported 393 by the ports system. However, all 32-bit platforms are Tier-2 394 or Tier-3 and support for individual ports should be expected 395 to degrade as upstreams deprecate 32-bit platforms. 396 397 With the current support schedule, stable/14 will be EOLed 5 398 years after the release of 14.0. The EOL of stable/14 would 399 mark the end of support for 32-bit platforms including source 400 releases, pre-built packages, and support for building 401 applications from ports. Given an estimated release date of 402 October 2023 for 14.0, support for 32-bit platforms would end 403 in October 2028. 404 405 The project may choose to alter this approach when 15.0 is 406 released by extending some level of 32-bit support for one or 407 more platforms in 15.0 or later. Users should use the 408 stable/14 branch to migrate off of 32-bit platforms. 409