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