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