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