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