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