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