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