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