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 13b22be3bbb2de: 14 Basic Cloudinit images no longer generate RSA host keys by default for 15 SSH. 16 17000000000000: 18 RSA host keys for SSH are deprecated and will no longer be generated 19 by default in FreeBSD 16. 20 210aabcd75dbc2: 22 EC2 AMIs no longer generate RSA host keys by default for SSH. RSA 23 host key generation can be re-enabled by setting sshd_rsa_enable="YES" 24 in /etc/rc.conf if it is necessary to support very old SSH clients. 25 26a1da7dc1cdad: 27 The SO_SPLICE socket option was added. It allows TCP connections to 28 be spliced together, enabling proxy-like functionality without the 29 need to copy data in and out of user memory. 30 31e962b37bf0ff: 32 When running bhyve(8) guests with a boot ROM, i.e., bhyveload(8) is not 33 used, bhyve now assumes that the boot ROM will enable PCI BAR decoding. 34 This is incompatible with some boot ROMs, particularly outdated builds 35 of edk2-bhyve. To restore the old behavior, add 36 "pci.enable_bars='true'" to your bhyve configuration. 37 38 Note in particular that the uefi-edk2-bhyve package has been renamed 39 to edk2-bhyve. 40 4143caa2e805c2: 42 amd64 bhyve(8)'s "lpc.bootrom" and "lpc.bootvars" options are 43 deprecated. Use the top-level "bootrom" and "bootvars" options 44 instead. 45 46822ca3276345: 47 byacc was updated to 20240109. 48 4921817992b331: 50 ncurses was updated to 6.5. 51 521687d77197c0: 53 Filesystem manual pages have been moved to section four. 54 Please check ports you are maintaining for crossreferences. 55 568aac90f18aef: 57 new MAC/do policy and mdo(1) utility which enables a user to 58 become another user without the requirement of setuid root. 59 607398d1ece5cf: 61 hw.snd.version is removed. 62 63a15f7c96a276,a8089ea5aee5: 64 NVMe over Fabrics controller. The nvmft(4) kernel module adds 65 a new frontend to the CAM target layer which exports ctl(4) 66 LUNs as NVMe namespaces to remote hosts. The nvmfd(8) daemon 67 is responsible for accepting incoming connection requests and 68 handing off connected queue pairs to nvmft(4). 69 70a1eda74167b5,1058c12197ab: 71 NVMe over Fabrics host. New commands added to nvmecontrol(8) 72 to establish connections to remote controllers. Once 73 connections are established they are handed off to the nvmf(4) 74 kernel module which creates nvmeX devices and exports remote 75 namespaces as nda(4) disks. 76 7725723d66369f: 78 As a side-effect of retiring the unit.* code in sound(4), the 79 hw.snd.maxunit loader(8) tunable is also retired. 80 81eeb04a736cb9: 82 date(1) now supports nanoseconds. For example: 83 `date -Ins` prints "2024-04-22T12:20:28,763742224+02:00" and 84 `date +%N` prints "415050400". 85 866d5ce2bb6344: 87 The default value of the nfs_reserved_port_only rc.conf(5) setting has 88 changed. The FreeBSD NFS server now requires the source port of 89 requests to be in the privileged port range (i.e., <= 1023), which 90 generally requires the client to have elevated privileges on their local 91 system. The previous behavior can be restored by setting 92 nfs_reserved_port_only=NO in rc.conf. 93 94aea973501b19: 95 ktrace(2) will now record detailed information about capability mode 96 violations. The kdump(1) utility has been updated to display such 97 information. 98 99f32a6403d346: 100 One True Awk updated to 2nd Edition. See https://awk.dev for details 101 on the additions. Unicode and CSVs (Comma Separated Values) are now 102 supported. 103 104fe86d923f83f: 105 usbconfig(8) now reads the descriptions of the usb vendor and products 106 from usb.ids when available, similarly to what pciconf(8) does. 107 1084347ef60501f: 109 The powerd(8) utility is now enabled in /etc/rc.conf by default on 110 images for the arm64 Raspberry Pi's (arm64-aarch64-RPI img files). 111 This prevents the CPU clock from running slow all the time. 112 1130b49e504a32d: 114 rc.d/jail now supports the legacy variable jail_${jailname}_zfs_dataset 115 to allow unmaintained jail managers like ezjail to make use of this 116 feature (simply rename jail_${jailname}_zfs_datasets in the ezjail 117 config to jail_${jailname}_zfs_dataset. 118 119e0dfe185cbca: 120 jail(8) now support zfs.dataset to add a list of ZFS datasets to a 121 jail. 122 12361174ad88e33: 124 newsyslog(8) now supports specifying a global compression method directly 125 at the beginning of the newsyslog.conf file, which will make newsyslog(8) 126 to behave like the corresponding option was passed to the newly added 127 '-c' option. For example: 128 129 <compress> none 130 131906748d208d3: 132 newsyslog(8) now accepts a new option, '-c' which overrides all historical 133 compression flags by treating their meaning as "treat the file as compressible" 134 rather than "compress the file with that specific method." 135 136 The following choices are available: 137 * none: Do not compress, regardless of flag. 138 * legacy: Historical behavior (J=bzip2, X=xz, Y=zstd, Z=gzip). 139 * bzip2, xz, zstd, gzip: apply the specified compression method. 140 141 We plan to change the default to 'none' in FreeBSD 15.0. 142 1431a878807006c: 144 This commit added some statistics collection to the NFS-over-TLS 145 code in the NFS server so that sysadmins can moditor usage. 146 The statistics are available via the kern.rpc.tls.* sysctls. 147 1487c5146da1286: 149 Mountd has been modified to use strunvis(3) to decode directory 150 names in exports(5) file(s). This allows special characters, 151 such as blanks, to be embedded in the directory name(s). 152 "vis -M" may be used to encode such directory name(s). 153 154c5359e2af5ab: 155 bhyve(8) has a new network backend, "slirp", which makes use of the 156 libslirp package to provide a userspace network stack. This backend 157 makes it possible to access the guest network from the host without 158 requiring any extra network configuration on the host. 159 160bb830e346bd5: 161 Set the IUTF8 flag by default in tty(4). 162 163 128f63cedc14 and 9e589b093857 added proper UTF-8 backspacing handling 164 in the tty(4) driver, which is enabled by setting the new IUTF8 flag 165 through stty(1). Since the default locale is UTF-8, enable IUTF8 by 166 default. 167 168ff01d71e48d4: 169 dialog(1) has been replaced by bsddialog(1) 170 17141582f28ddf7: 172 FreeBSD 15.0 will not include support for 32-bit platforms. 173 However, 64-bit systems will still be able to run older 32-bit 174 binaries. 175 176 Support for executing 32-bit binaries on 64-bit platforms via 177 COMPAT_FREEBSD32 will remain supported for at least the 178 stable/15 and stable/16 branches. 179 180 Support for compiling individual 32-bit applications via 181 `cc -m32` will also be supported for at least the stable/15 182 branch which includes suitable headers in /usr/include and 183 libraries in /usr/lib32. 184 185 Support for 32-bit platforms in ports for 15.0 and later 186 releases is also deprecated, and these future releases may not 187 include binary packages for 32-bit platforms or support for 188 building 32-bit applications from ports. 189 190 stable/14 and earlier branches will retain existing 32-bit 191 kernel and world support. Ports will retain existing support 192 for building ports and packages for 32-bit systems on stable/14 193 and earlier branches as long as those branches are supported 194 by the ports system. However, all 32-bit platforms are Tier-2 195 or Tier-3 and support for individual ports should be expected 196 to degrade as upstreams deprecate 32-bit platforms. 197 198 With the current support schedule, stable/14 will be EOLed 5 199 years after the release of 14.0. The EOL of stable/14 would 200 mark the end of support for 32-bit platforms including source 201 releases, pre-built packages, and support for building 202 applications from ports. Given an estimated release date of 203 October 2023 for 14.0, support for 32-bit platforms would end 204 in October 2028. 205 206 The project may choose to alter this approach when 15.0 is 207 released by extending some level of 32-bit support for one or 208 more platforms in 15.0 or later. Users should use the 209 stable/14 branch to migrate off of 32-bit platforms. 210