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