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