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