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 135dc99e9bb985, 08e638c089a, 4009a98fe80: 14 The net.inet.{tcp,udp,raw}.bind_all_fibs tunables have been added. 15 They modify socket behavior such that packets not originating from the 16 same FIB as the socket are ignored. TCP and UDP sockets belonging to 17 different FIBs may also be bound to the same address. The default 18 behavior is unmodified. 19 20f87bb5967670, e51036fbf3f8: 21 Support for vinum volumes has been removed. 22 238ae6247aa966, cf0ede720391d, 205659c43d87bd, 1ccbdf561f417, 4db1b113b151: 24 The layout of NFS file handles for the tarfs, tmpfs, cd9660, and ext2fs 25 file systems has changed. An NFS server that exports any of these file 26 systems will need its clients to unmount and remount the exports. 27 281111a44301da: 29 Defer the January 19, 2038 date limit in UFS1 filesystems to 30 February 7, 2106. This affects only UFS1 format filesystems. 31 See the commit message for details. 32 3307cd69e272da: 34 Add a new -a command line option to mountd(8). 35 If this command line option is specified, when 36 a line in exports(5) has the -alldirs export option, 37 the directory must be a server file system mount point. 38 390e8a36a2ab12: 40 Add a new NFS mount option called "mountport" that may be used 41 to specify the port# for the NFS server's Mount protocol. 42 This permits a NFSv3 mount to be done without running rpcbind(8). 43 44b2f7c53430c3: 45 Kernel TLS is now enabled by default in kernels including KTLS 46 support. KTLS is included in GENERIC kernels for aarch64, 47 amd64, powerpc64, and powerpc64le. 48 49f57efe95cc25: 50 New mididump(1) utility which dumps MIDI 1.0 events in real time. 51 52ddfc6f84f242: 53 Update unicode to 16.0.0 and CLDR to 45.0.0. 54 55b22be3bbb2de: 56 Basic Cloudinit images no longer generate RSA host keys by default for 57 SSH. 58 59000000000000: 60 RSA host keys for SSH are deprecated and will no longer be generated 61 by default in FreeBSD 16. 62 630aabcd75dbc2: 64 EC2 AMIs no longer generate RSA host keys by default for SSH. RSA 65 host key generation can be re-enabled by setting sshd_rsa_enable="YES" 66 in /etc/rc.conf if it is necessary to support very old SSH clients. 67 68a1da7dc1cdad: 69 The SO_SPLICE socket option was added. It allows TCP connections to 70 be spliced together, enabling proxy-like functionality without the 71 need to copy data in and out of user memory. 72 73fc12c191c087: 74 grep(1) no longer follows symbolic links by default for 75 recursive searches. This matches the documented behavior in 76 the manual page. 77 78e962b37bf0ff: 79 When running bhyve(8) guests with a boot ROM, i.e., bhyveload(8) is not 80 used, bhyve now assumes that the boot ROM will enable PCI BAR decoding. 81 This is incompatible with some boot ROMs, particularly outdated builds 82 of edk2-bhyve. To restore the old behavior, add 83 "pci.enable_bars='true'" to your bhyve configuration. 84 85 Note in particular that the uefi-edk2-bhyve package has been renamed 86 to edk2-bhyve. 87 8843caa2e805c2: 89 amd64 bhyve(8)'s "lpc.bootrom" and "lpc.bootvars" options are 90 deprecated. Use the top-level "bootrom" and "bootvars" options 91 instead. 92 93822ca3276345: 94 byacc was updated to 20240109. 95 9621817992b331: 97 ncurses was updated to 6.5. 98 991687d77197c0: 100 Filesystem manual pages have been moved to section four. 101 Please check ports you are maintaining for crossreferences. 102 1038aac90f18aef: 104 new MAC/do policy and mdo(1) utility which enables a user to 105 become another user without the requirement of setuid root. 106 1077398d1ece5cf: 108 hw.snd.version is removed. 109 110a15f7c96a276,a8089ea5aee5: 111 NVMe over Fabrics controller. The nvmft(4) kernel module adds 112 a new frontend to the CAM target layer which exports ctl(4) 113 LUNs as NVMe namespaces to remote hosts. The nvmfd(8) daemon 114 is responsible for accepting incoming connection requests and 115 handing off connected queue pairs to nvmft(4). 116 117a1eda74167b5,1058c12197ab: 118 NVMe over Fabrics host. New commands added to nvmecontrol(8) 119 to establish connections to remote controllers. Once 120 connections are established they are handed off to the nvmf(4) 121 kernel module which creates nvmeX devices and exports remote 122 namespaces as nda(4) disks. 123 12425723d66369f: 125 As a side-effect of retiring the unit.* code in sound(4), the 126 hw.snd.maxunit loader(8) tunable is also retired. 127 128eeb04a736cb9: 129 date(1) now supports nanoseconds. For example: 130 `date -Ins` prints "2024-04-22T12:20:28,763742224+02:00" and 131 `date +%N` prints "415050400". 132 1336d5ce2bb6344: 134 The default value of the nfs_reserved_port_only rc.conf(5) setting has 135 changed. The FreeBSD NFS server now requires the source port of 136 requests to be in the privileged port range (i.e., <= 1023), which 137 generally requires the client to have elevated privileges on their local 138 system. The previous behavior can be restored by setting 139 nfs_reserved_port_only=NO in rc.conf. 140 141aea973501b19: 142 ktrace(2) will now record detailed information about capability mode 143 violations. The kdump(1) utility has been updated to display such 144 information. 145 146f32a6403d346: 147 One True Awk updated to 2nd Edition. See https://awk.dev for details 148 on the additions. Unicode and CSVs (Comma Separated Values) are now 149 supported. 150 151fe86d923f83f: 152 usbconfig(8) now reads the descriptions of the usb vendor and products 153 from usb.ids when available, similarly to what pciconf(8) does. 154 1554347ef60501f: 156 The powerd(8) utility is now enabled in /etc/rc.conf by default on 157 images for the arm64 Raspberry Pi's (arm64-aarch64-RPI img files). 158 This prevents the CPU clock from running slow all the time. 159 1600b49e504a32d: 161 rc.d/jail now supports the legacy variable jail_${jailname}_zfs_dataset 162 to allow unmaintained jail managers like ezjail to make use of this 163 feature (simply rename jail_${jailname}_zfs_datasets in the ezjail 164 config to jail_${jailname}_zfs_dataset. 165 166e0dfe185cbca: 167 jail(8) now support zfs.dataset to add a list of ZFS datasets to a 168 jail. 169 17061174ad88e33: 171 newsyslog(8) now supports specifying a global compression method directly 172 at the beginning of the newsyslog.conf file, which will make newsyslog(8) 173 to behave like the corresponding option was passed to the newly added 174 '-c' option. For example: 175 176 <compress> none 177 178906748d208d3: 179 newsyslog(8) now accepts a new option, '-c' which overrides all historical 180 compression flags by treating their meaning as "treat the file as compressible" 181 rather than "compress the file with that specific method." 182 183 The following choices are available: 184 * none: Do not compress, regardless of flag. 185 * legacy: Historical behavior (J=bzip2, X=xz, Y=zstd, Z=gzip). 186 * bzip2, xz, zstd, gzip: apply the specified compression method. 187 188 We plan to change the default to 'none' in FreeBSD 15.0. 189 1901a878807006c: 191 This commit added some statistics collection to the NFS-over-TLS 192 code in the NFS server so that sysadmins can moditor usage. 193 The statistics are available via the kern.rpc.tls.* sysctls. 194 1957c5146da1286: 196 Mountd has been modified to use strunvis(3) to decode directory 197 names in exports(5) file(s). This allows special characters, 198 such as blanks, to be embedded in the directory name(s). 199 "vis -M" may be used to encode such directory name(s). 200 201c5359e2af5ab: 202 bhyve(8) has a new network backend, "slirp", which makes use of the 203 libslirp package to provide a userspace network stack. This backend 204 makes it possible to access the guest network from the host without 205 requiring any extra network configuration on the host. 206 207bb830e346bd5: 208 Set the IUTF8 flag by default in tty(4). 209 210 128f63cedc14 and 9e589b093857 added proper UTF-8 backspacing handling 211 in the tty(4) driver, which is enabled by setting the new IUTF8 flag 212 through stty(1). Since the default locale is UTF-8, enable IUTF8 by 213 default. 214 215ff01d71e48d4: 216 dialog(1) has been replaced by bsddialog(1) 217 21841582f28ddf7: 219 FreeBSD 15.0 will not include support for 32-bit platforms. 220 However, 64-bit systems will still be able to run older 32-bit 221 binaries. 222 223 Support for executing 32-bit binaries on 64-bit platforms via 224 COMPAT_FREEBSD32 will remain supported for at least the 225 stable/15 and stable/16 branches. 226 227 Support for compiling individual 32-bit applications via 228 `cc -m32` will also be supported for at least the stable/15 229 branch which includes suitable headers in /usr/include and 230 libraries in /usr/lib32. 231 232 Support for 32-bit platforms in ports for 15.0 and later 233 releases is also deprecated, and these future releases may not 234 include binary packages for 32-bit platforms or support for 235 building 32-bit applications from ports. 236 237 stable/14 and earlier branches will retain existing 32-bit 238 kernel and world support. Ports will retain existing support 239 for building ports and packages for 32-bit systems on stable/14 240 and earlier branches as long as those branches are supported 241 by the ports system. However, all 32-bit platforms are Tier-2 242 or Tier-3 and support for individual ports should be expected 243 to degrade as upstreams deprecate 32-bit platforms. 244 245 With the current support schedule, stable/14 will be EOLed 5 246 years after the release of 14.0. The EOL of stable/14 would 247 mark the end of support for 32-bit platforms including source 248 releases, pre-built packages, and support for building 249 applications from ports. Given an estimated release date of 250 October 2023 for 14.0, support for 32-bit platforms would end 251 in October 2028. 252 253 The project may choose to alter this approach when 15.0 is 254 released by extending some level of 32-bit support for one or 255 more platforms in 15.0 or later. Users should use the 256 stable/14 branch to migrate off of 32-bit platforms. 257