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