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