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