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 131a878807006c: 14 This commit added some statistics collection to the NFS-over-TLS 15 code in the NFS server so that sysadmins can moditor usage. 16 The statistics are available via the kern.rpc.tls.* sysctls. 17 187c5146da1286: 19 Mountd has been modified to use strunvis(3) to decode directory 20 names in exports(5) file(s). This allows special characters, 21 such as blanks, to be embedded in the directory name(s). 22 "vis -M" may be used to encode such directory name(s). 23 24c5359e2af5ab: 25 bhyve(8) has a new network backend, "slirp", which makes use of the 26 libslirp package to provide a userspace network stack. This backend 27 makes it possible to access the guest network from the host without 28 requiring any extra network configuration on the host. 29 30bb830e346bd5: 31 Set the IUTF8 flag by default in tty(4). 32 33 128f63cedc14 and 9e589b093857 added proper UTF-8 backspacing handling 34 in the tty(4) driver, which is enabled by setting the new IUTF8 flag 35 through stty(1). Since the default locale is UTF-8, enable IUTF8 by 36 default. 37 38ff01d71e48d4: 39 dialog(1) has been replaced by bsddialog(1) 40 4141582f28ddf7: 42 FreeBSD 15.0 will not include support for 32-bit platforms. 43 However, 64-bit systems will still be able to run older 32-bit 44 binaries. 45 46 Support for executing 32-bit binaries on 64-bit platforms via 47 COMPAT_FREEBSD32 will remain supported for at least the 48 stable/15 and stable/16 branches. 49 50 Support for compiling individual 32-bit applications via 51 `cc -m32` will also be supported for at least the stable/15 52 branch which includes suitable headers in /usr/include and 53 libraries in /usr/lib32. 54 55 Support for 32-bit platforms in ports for 15.0 and later 56 releases is also deprecated, and these future releases may not 57 include binary packages for 32-bit platforms or support for 58 building 32-bit applications from ports. 59 60 stable/14 and earlier branches will retain existing 32-bit 61 kernel and world support. Ports will retain existing support 62 for building ports and packages for 32-bit systems on stable/14 63 and earlier branches as long as those branches are supported 64 by the ports system. However, all 32-bit platforms are Tier-2 65 or Tier-3 and support for individual ports should be expected 66 to degrade as upstreams deprecate 32-bit platforms. 67 68 With the current support schedule, stable/14 will be EOLed 5 69 years after the release of 14.0. The EOL of stable/14 would 70 mark the end of support for 32-bit platforms including source 71 releases, pre-built packages, and support for building 72 applications from ports. Given an estimated release date of 73 October 2023 for 14.0, support for 32-bit platforms would end 74 in October 2028. 75 76 The project may choose to alter this approach when 15.0 is 77 released by extending some level of 32-bit support for one or 78 more platforms in 15.0 or later. Users should use the 79 stable/14 branch to migrate off of 32-bit platforms. 80