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 130b49e504a32d: 14 rc.d/jail now supports the legacy variable jail_${jailname}_zfs_dataset 15 to allow unmaintained jail managers like ezjail to make use of this 16 feature (simply rename jail_${jailname}_zfs_datasets in the ezjail 17 config to jail_${jailname}_zfs_dataset. 18 19e0dfe185cbca: 20 jail(8) now support zfs.dataset to add a list of ZFS datasets to a 21 jail. 22 2361174ad88e33: 24 newsyslog(8) now supports specifying a global compression method directly 25 at the beginning of the newsyslog.conf file, which will make newsyslog(8) 26 to behave like the corresponding option was passed to the newly added 27 '-c' option. For example: 28 29 <compress> none 30 31906748d208d3: 32 newsyslog(8) now accepts a new option, '-c' which overrides all historical 33 compression flags by treating their meaning as "treat the file as compressible" 34 rather than "compress the file with that specific method." 35 36 The following choices are available: 37 * none: Do not compress, regardless of flag. 38 * legacy: Historical behavior (J=bzip2, X=xz, Y=zstd, Z=gzip). 39 * bzip2, xz, zstd, gzip: apply the specified compression method. 40 41 We plan to change the default to 'none' in FreeBSD 15.0. 42 431a878807006c: 44 This commit added some statistics collection to the NFS-over-TLS 45 code in the NFS server so that sysadmins can moditor usage. 46 The statistics are available via the kern.rpc.tls.* sysctls. 47 487c5146da1286: 49 Mountd has been modified to use strunvis(3) to decode directory 50 names in exports(5) file(s). This allows special characters, 51 such as blanks, to be embedded in the directory name(s). 52 "vis -M" may be used to encode such directory name(s). 53 54c5359e2af5ab: 55 bhyve(8) has a new network backend, "slirp", which makes use of the 56 libslirp package to provide a userspace network stack. This backend 57 makes it possible to access the guest network from the host without 58 requiring any extra network configuration on the host. 59 60bb830e346bd5: 61 Set the IUTF8 flag by default in tty(4). 62 63 128f63cedc14 and 9e589b093857 added proper UTF-8 backspacing handling 64 in the tty(4) driver, which is enabled by setting the new IUTF8 flag 65 through stty(1). Since the default locale is UTF-8, enable IUTF8 by 66 default. 67 68ff01d71e48d4: 69 dialog(1) has been replaced by bsddialog(1) 70 7141582f28ddf7: 72 FreeBSD 15.0 will not include support for 32-bit platforms. 73 However, 64-bit systems will still be able to run older 32-bit 74 binaries. 75 76 Support for executing 32-bit binaries on 64-bit platforms via 77 COMPAT_FREEBSD32 will remain supported for at least the 78 stable/15 and stable/16 branches. 79 80 Support for compiling individual 32-bit applications via 81 `cc -m32` will also be supported for at least the stable/15 82 branch which includes suitable headers in /usr/include and 83 libraries in /usr/lib32. 84 85 Support for 32-bit platforms in ports for 15.0 and later 86 releases is also deprecated, and these future releases may not 87 include binary packages for 32-bit platforms or support for 88 building 32-bit applications from ports. 89 90 stable/14 and earlier branches will retain existing 32-bit 91 kernel and world support. Ports will retain existing support 92 for building ports and packages for 32-bit systems on stable/14 93 and earlier branches as long as those branches are supported 94 by the ports system. However, all 32-bit platforms are Tier-2 95 or Tier-3 and support for individual ports should be expected 96 to degrade as upstreams deprecate 32-bit platforms. 97 98 With the current support schedule, stable/14 will be EOLed 5 99 years after the release of 14.0. The EOL of stable/14 would 100 mark the end of support for 32-bit platforms including source 101 releases, pre-built packages, and support for building 102 applications from ports. Given an estimated release date of 103 October 2023 for 14.0, support for 32-bit platforms would end 104 in October 2028. 105 106 The project may choose to alter this approach when 15.0 is 107 released by extending some level of 32-bit support for one or 108 more platforms in 15.0 or later. Users should use the 109 stable/14 branch to migrate off of 32-bit platforms. 110