1 Release notes for FreeBSD 15.0.
3 This file describes new user-visible features, changes and updates relevant to
4 users of binary FreeBSD releases. Each entry should describe the change in no
5 more than several sentences and should reference manual pages where an
6 interested user can find more information. Entries should wrap after 80
7 columns. Each entry should begin with one or more commit IDs on one line,
8 specified as a comma separated list and/or range, followed by a colon and a
9 newline. Entries should be separated by a newline.
11 Changes to this file should not be MFCed.
14 As a side-effect of retiring the unit.* code in sound(4), the
15 hw.snd.maxunit loader(8) tunable is also retired.
17 The default value of the nfs_reserved_port_only rc.conf(5) setting has
18 changed. The FreeBSD NFS server now requires the source port of
19 requests to be in the privileged port range (i.e., <= 1023), which
20 generally requires the client to have elevated privileges on their local
21 system. The previous behavior can be restored by setting
22 nfs_reserved_port_only=NO in rc.conf.
25 ktrace(2) will now record detailed information about capability mode
26 violations. The kdump(1) utility has been updated to display such
30 One True Awk updated to 2nd Edition. See https://awk.dev for details
31 on the additions. Unicode and CSVs (Comma Separated Values) are now
35 usbconfig(8) now reads the descriptions of the usb vendor and products
36 from usb.ids when available, similarly to what pciconf(8) does.
39 The powerd(8) utility is now enabled in /etc/rc.conf by default on
40 images for the arm64 Raspberry Pi's (arm64-aarch64-RPI img files).
41 This prevents the CPU clock from running slow all the time.
44 rc.d/jail now supports the legacy variable jail_${jailname}_zfs_dataset
45 to allow unmaintained jail managers like ezjail to make use of this
46 feature (simply rename jail_${jailname}_zfs_datasets in the ezjail
47 config to jail_${jailname}_zfs_dataset.
50 jail(8) now support zfs.dataset to add a list of ZFS datasets to a
54 newsyslog(8) now supports specifying a global compression method directly
55 at the beginning of the newsyslog.conf file, which will make newsyslog(8)
56 to behave like the corresponding option was passed to the newly added
57 '-c' option. For example:
62 newsyslog(8) now accepts a new option, '-c' which overrides all historical
63 compression flags by treating their meaning as "treat the file as compressible"
64 rather than "compress the file with that specific method."
66 The following choices are available:
67 * none: Do not compress, regardless of flag.
68 * legacy: Historical behavior (J=bzip2, X=xz, Y=zstd, Z=gzip).
69 * bzip2, xz, zstd, gzip: apply the specified compression method.
71 We plan to change the default to 'none' in FreeBSD 15.0.
74 This commit added some statistics collection to the NFS-over-TLS
75 code in the NFS server so that sysadmins can moditor usage.
76 The statistics are available via the kern.rpc.tls.* sysctls.
79 Mountd has been modified to use strunvis(3) to decode directory
80 names in exports(5) file(s). This allows special characters,
81 such as blanks, to be embedded in the directory name(s).
82 "vis -M" may be used to encode such directory name(s).
85 bhyve(8) has a new network backend, "slirp", which makes use of the
86 libslirp package to provide a userspace network stack. This backend
87 makes it possible to access the guest network from the host without
88 requiring any extra network configuration on the host.
91 Set the IUTF8 flag by default in tty(4).
93 128f63cedc14 and 9e589b093857 added proper UTF-8 backspacing handling
94 in the tty(4) driver, which is enabled by setting the new IUTF8 flag
95 through stty(1). Since the default locale is UTF-8, enable IUTF8 by
99 dialog(1) has been replaced by bsddialog(1)
102 FreeBSD 15.0 will not include support for 32-bit platforms.
103 However, 64-bit systems will still be able to run older 32-bit
106 Support for executing 32-bit binaries on 64-bit platforms via
107 COMPAT_FREEBSD32 will remain supported for at least the
108 stable/15 and stable/16 branches.
110 Support for compiling individual 32-bit applications via
111 `cc -m32` will also be supported for at least the stable/15
112 branch which includes suitable headers in /usr/include and
113 libraries in /usr/lib32.
115 Support for 32-bit platforms in ports for 15.0 and later
116 releases is also deprecated, and these future releases may not
117 include binary packages for 32-bit platforms or support for
118 building 32-bit applications from ports.
120 stable/14 and earlier branches will retain existing 32-bit
121 kernel and world support. Ports will retain existing support
122 for building ports and packages for 32-bit systems on stable/14
123 and earlier branches as long as those branches are supported
124 by the ports system. However, all 32-bit platforms are Tier-2
125 or Tier-3 and support for individual ports should be expected
126 to degrade as upstreams deprecate 32-bit platforms.
128 With the current support schedule, stable/14 will be EOLed 5
129 years after the release of 14.0. The EOL of stable/14 would
130 mark the end of support for 32-bit platforms including source
131 releases, pre-built packages, and support for building
132 applications from ports. Given an estimated release date of
133 October 2023 for 14.0, support for 32-bit platforms would end
136 The project may choose to alter this approach when 15.0 is
137 released by extending some level of 32-bit support for one or
138 more platforms in 15.0 or later. Users should use the
139 stable/14 branch to migrate off of 32-bit platforms.