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