Differential D42304 Diff 129188 website/content/en/releases/14.0R/relnotes.adoc

Changeset View

Standalone View

View Options

website/content/en/releases/14.0R/relnotes.adoc

Show All 14 Lines

:doctype: article

:toc: macro

:toclevels: 1

:icons: font

== Abstract

[.abstract-title]

The release notes for FreeBSD {releaseCurrent} contain a summary of the changes made to the FreeBSD base system on the {releaseBranch} development line. This document lists applicable security advisories that were issued since the last release, as well as significant changes to the FreeBSD kernel and userland. Some brief remarks on upgrading are also presented.

The release notes for FreeBSD {releaseCurrent} contain a summary of the changes made to the FreeBSD base system on the {releaseBranch} development line.

This document lists applicable security advisories that were issued since the last release, as well as significant changes to the FreeBSD kernel and userland.

Some brief remarks on upgrading are also presented.

[[intro]]

== Introduction

This document contains the release notes for FreeBSD {releaseCurrent}. It describes recently added, changed, or deleted features of FreeBSD. It also provides some notes on upgrading from previous versions of FreeBSD.

This document contains the release notes for FreeBSD {releaseCurrent}.

It describes recently added, changed, or deleted features of FreeBSD.

It also provides some notes on upgrading from previous versions of FreeBSD.

The {releaseType} distribution to which these release notes apply represents the latest point along the {releaseBranch} development branch since {releaseBranch} was created. Information regarding pre-built, binary {releaseType} distributions along this branch can be found at https://www.FreeBSD.org/releases/[https://www.FreeBSD.org/releases/].

The {releaseType} distribution to which these release notes apply represents the latest point along the {releaseBranch} development branch since {releaseBranch} was created.

Information regarding pre-built, binary {releaseType} distributions along this branch can be found at https://www.FreeBSD.org/releases/[].

The {releaseType} distribution to which these release notes apply represents a point along the {releaseBranch} development branch between {releasePrev} and the future {releaseNext}. Information regarding pre-built, binary {releaseType} distributions along this branch can be found at https://www.FreeBSD.org/releases/[https://www.FreeBSD.org/releases/].

The {releaseType} distribution to which these release notes apply represents a point along the {releaseBranch} development branch between {releasePrev} and the future {releaseNext}.

Information regarding pre-built, binary {releaseType} distributions along this branch can be found at https://www.FreeBSD.org/releases/[].

This distribution of FreeBSD {releaseCurrent} is a {releaseType} distribution. It can be found at https://www.FreeBSD.org/releases/[https://www.FreeBSD.org/releases/] or any of its mirrors. More information on obtaining this (or other) {releaseType} distributions of FreeBSD can be found in the link:{handbook}mirrors[Obtaining FreeBSD appendix] to the link:{handbook}[FreeBSD Handbook].

This distribution of FreeBSD {releaseCurrent} is a {releaseType} distribution.

It can be found at https://www.FreeBSD.org/releases/[] or any of its mirrors.

More information on obtaining this (or other) {releaseType} distributions of FreeBSD can be found in the link:{handbook}mirrors[Obtaining FreeBSD appendix] to the link:{handbook}[FreeBSD Handbook].

All users are encouraged to consult the release errata before installing FreeBSD. The errata document is updated with "late-breaking" information discovered late in the release cycle or after the release. Typically, it contains information on known bugs, security advisories, and corrections to documentation. An up-to-date copy of the errata for FreeBSD {releaseCurrent} can be found on the FreeBSD Web site.

All users are encouraged to consult the release errata before installing FreeBSD.

The errata document is updated with "late-breaking" information discovered late in the release cycle or after the release.

Typically, it contains information on known bugs, security advisories, and corrections to documentation.

An up-to-date copy of the errata for FreeBSD {releaseCurrent} can be found on the FreeBSD Web site.

This document describes the most user-visible new or changed features in FreeBSD since {releasePrev}. In general, changes described here are unique to the {releaseBranch} branch unless specifically marked as MERGED features.

This document describes the most user-visible new or changed features in FreeBSD since {releasePrev}.

In general, changes described here are unique to the {releaseBranch} branch unless specifically marked as MERGED features.

Typical release note items document recent security advisories issued after {releasePrev}, new drivers or hardware support, new commands or options, major bug fixes, or contributed software upgrades. They may also list changes to major ports/packages or release engineering practices. Clearly the release notes cannot list every single change made to FreeBSD between releases; this document focuses primarily on security advisories, user-visible changes, and major architectural improvements.

Typical release note items document recent security advisories issued after {releasePrev}, new drivers or hardware support, new commands or options, major bug fixes, or contributed software upgrades.

They may also list changes to major ports/packages or release engineering practices.

Clearly the release notes cannot list every single change made to FreeBSD between releases; this document focuses primarily on security advisories, user-visible changes, and major architectural improvements.

[[upgrade]]

== Upgrading from Previous Releases of FreeBSD

Binary upgrades between RELEASE versions (and snapshots of the various security branches) are supported using the man:freebsd-update[8] utility. The binary upgrade procedure will update unmodified userland utilities, as well as unmodified GENERIC kernels distributed as a part of an official FreeBSD release. The man:freebsd-update[8] utility requires that the host being upgraded have Internet connectivity.

Binary upgrades between RELEASE versions (and snapshots of the various security branches) are supported using the man:freebsd-update[8] utility.

The binary upgrade procedure will update unmodified userland utilities, as well as unmodified GENERIC kernels distributed as a part of an official FreeBSD release.

The man:freebsd-update[8] utility requires that the host being upgraded have Internet connectivity.

Source-based upgrades (those based on recompiling the FreeBSD base system from source code) from previous versions are supported, according to the instructions in [.filename]#/usr/src/UPDATING#.

Note for systems that boot from a ZFS root filesystem via EFI, using either binary or source upgrades:

There are one or more copies of the boot loader on the MS-DOS EFI System Partition (ESP), used by the firmware to boot the kernel, and which must be able to support reading from the ZFS boot file system.

After a system upgrade, but before doing a `zpool upgrade`, the boot loader on the ESP must be updated, or the system may become unbootable.

The location of the boot loader in use can be determined using the command `efibootmgr -v`.

The value displayed for `BootCurrent` should be the number of the current boot configuration used to boot the system.

The corresponding line of the output should begin with a `+` sign, such as

+Boot0000* FreeBSD HD(1,GPT,f859c46d-19ee-4e40-8975-3ad1ab00ac09,0x800,0x82000)/File(\EFI\freebsd\loader.efi)

nda0p1:/EFI/freebsd/loader.efi (null)

The ESP may already be mounted on [.filename]#/boot/efi#.

//If not, a `noauto` entry may be in the man:fstab[5] file; this allows the command `mount /boot/efi` to mount the file system.

Otherwise, the partition may be mounted manually, using the partition listed in the `efibootmgr` output (`nda0p1` in this case): `mount_msdosfs /dev/nda0p1 /boot/efi`.

See man:loader.efi[8] for another example.

The value in the `File` field in the `efibootmgr -v` output, `\EFI\freebsd\loader.efi` in this case, is the MS-DOS name for the boot loader in use on the ESP.

If the mount point is `/boot/efi`, this file will translate to `/boot/efi/efi/freebsd/loader.efi`.

(Case does not matter on MS-DOSFS file sytems; FreeBSD uses lower case.)

Another common value for File would be `\EFI\boot\bootXXX.efi`, where `XXX` is `x64` for amd64, `aa64` for aarch64, or `riscv64` for riscv64; this is the default bootstrap if none is configured.

Another common value for `File` would be `\EFI\boot\bootXXX.efi`, where `XXX` is `x64` for amd64, `aa64` for aarch64, or `riscv64` for riscv64; this is the default bootstrap if none is configured.

Both the configured and default boot loaders should be updated by copying from [.filename]#/boot/loader.efi# to the correct path in `/boot/efi`.

[IMPORTANT]

====

Upgrading FreeBSD should only be attempted after backing up _all_ data and configuration files.

====

[[security-errata]]

Show All 26 Lines

| Errata

| Date

| Topic

|No notices.

|===

////

// Sample release notes entry.

//The man:fsck_msdosfs[8] utility includes a variety of enhancements, including reducing the memory footprint, a new flag, `-M`, which disables the use of man:mmap[2], and others. gitref:9708ba9f29[repository=src]

The man:fsck_msdosfs[8] utility includes a variety of enhancements, including reducing the memory footprint, a new flag, `-M`, which disables the use of man:mmap[2], and others.

gitref:9708ba9f29[repository=src]

////

[[userland]]

== Userland

This section covers changes and additions to userland applications, contributed software, and system utilities.

[[userland-config]]

=== Userland Configuration Changes

The default shell for the root user is now man:sh[1], which now has many features for interactive use.

The default shell for the root user is now man:sh[1], which has many new features for interactive use.

gitref:d410b585b6f0[repository=src]

The default mail transport agent is now the Dragonfly Mail Agent (man:dma[8]), replacing man:sendmail[8].

The default mail transport agent (MTA) is now the Dragonfly Mail Agent (man:dma[8]) rather than man:sendmail[8].

Configuration of the mail transport agent is done via man:mailer.conf[5].

Configuration of the MTA is done via man:mailer.conf[5].

man:sendmail[8] and its configuration remain available.

gitref:a67b925ff3e5[repository=src]

The `mta_start_script` configuration variable has been retired in man:rc.conf[5], along with the `othermta` startup script.

The `mta_start_script` configuration variable has been retired from man:rc.conf[5], along with the `othermta` startup script.

gitref:616f32ea6da7[repository=src]

man:jail[8] now supports `.include` directives in man:jail.conf[5] files, with support for filename globbing.

gitref:e82a62943529[repository=src]

The one-time password facility OPIE, man:opie[4], has been removed from the base system.

If you still wish to use it, install the `security/opie` port.

If you still wish to use it, install the package:security/opie[] port.

Otherwise, make sure to remove or comment out any mention of `pam_opie` and `pam_opieaccess` from your PAM policies.

man:etcupdate[8] will normally take care of this for the stock policies.

gitref:0aa2700123e2[repository=src]

The `SHARED_TOOLCHAIN` build configuration option has been removed.

Building a statically-linked toolchain is still possible using the general `NO_SHARED` option.

gitref:77f6be448408[repository=src] (Sponsored by The FreeBSD Foundation)

Show All 15 Lines

The man:date[1] utility now has a `-z` option for timezone conversion.

gitref:31edf56b1571[repository=src]

The deprecated man:fmtree[8] utility has been removed.

gitref:e4d63c5d5ff8[repository=src]

A new man:fwget[8] utility inspects the system for peripherals that need firmware, and installs the appropriate packages for them.

For now only the PCI subsystem is supported, and only video firmware for Intel and AMD GPUs is known.

For now, only the PCI subsystem is supported, and only video firmware for Intel and AMD GPUs is known.

gitref:d198b8774d2c[repository=src] gitref:d198b8774d2c[repository=src] (Sponsored by Beckhoff Automation GmbH & Co. KG)

The usability of man:head[1] and man:tail[1] has been improved by consistently supporting the `-q` and `-h` options, allowing numbers with SI suffixes, and removing the 2^31 limit on lines for man:head[1].

gitref:643ac419fafb[repository=src]

man:makefs[8] now has experimental ZFS support.

It can create a ZFS pool, backed by a single disk vdev, containing one or more datasets populated from the staging directory.

gitref:240afd8c1fcc[repository=src] (Sponsored by The FreeBSD Foundation)

The man:minigzip[1] utility has been removed.

gitref:278d080bad9F[REPOSITory=src]

The man:mandoc[1] utility has a workaround for lack of macro processing in list `-width` handling, resulting in more accurate widths for list columns.

gitref:bbb2d2ce4220[repository=src] (Sponsored by Dell EMC Isilon)

The man:mixer[8] utility no longer tries to guess whether a volume is absolute or a percent.

It now accepts a percentage with a `%` appended, otherwise a volume is absolute.

It now accepts a percentage with `%` appended, otherwise a volume is absolute.

gitref:4014365e4219[repository=src]

The `netcat` utility man:nc[1] can now be an `if_tun` (man:tun[4]) broker.

gitref:cef7ab70ff44[repository=src] (Sponsored by Zenarmor) (Sponsored by OPNsense) (Sponsored by Klara, Inc.)

The man:netstat[1] utility now computes correct column widths with the `-i` option, making the `-w` option unnecessary.

gitref:372e3d561d82[repository=src]

The man:portsnap[8] utility has been removed.

Users are encouraged to fetch the ports tree by using `pkg install git` and then `git clone https://git.FreeBSD.org/ports.git /usr/ports`.

Users are encouraged to fetch the ports tree by using `pkg install git` and then `git clone \https://git.FreeBSD.org/ports.git /usr/ports`.

gitref:df53ae0fdd98[repository=src]

The man:pw[8] and man:bsdinstall[8] programs now create home directories for users in [.filename]#/home# by default rather than [.filename]#/usr/home#.

The default symbolic link for [.filename]#/home#, referencing [.filename]#/usr/home#, is no longer created.

gitref:bbb2d2ce4220[repository=src]

The man:sleep[1] utility now accepts units other than seconds, and accepts multiple delay values that are summed.

gitref:34978f7edd15[repository=src] gitref:be038c3afcae[repository=src]

The man:sockstat[1] utility is now run in a sandbox with capsicum.

gitref:94dc57159532[repository=src] gitref:c5a2d8c5f517[repository=src]

The man:systat[1] utility has a new command, `iolat`, which reports I/O latencies computed by the CAM I/O scheduler.

gitref:22054f88914b[repository=src] (Sponsored by Netflix)

A new utility, man:tcpsso[8], is able to apply a socket option to an existing TCP endpoint, for example changing the congestion control module or the TCP stack.

gitref:881631a2a371[repository=src] (Sponsored by Netflix)

The Telnet daemon, man:telnetd[8], has been removed.

A port is available if necessary, `net/freebsd-telnetd`.

A port is available if necessary, package:net/freebsd-telnetd[].

The client is not affected.

gitref:0eea46fb1f83[repository=src]

The `PROFILE` option is disabled by default, thus profiled versions of system libraries are not provided.

Hardware-based profiling (e.g. man:hwpmc[4]) is preferred.

gitref:fe52b7f60ef4[repository=src] (Sponsored by The FreeBSD Foundation)

Compressed debug sections in binaries are enabled by default on little-endian targets.

Show All 23 Lines

The man:llvm-objdump[1] utility is now always installed as man:objdump[1].

gitref:86edb11e7491[repository=src] (Sponsored by The FreeBSD Foundation)

OpenSSH has been upgraded to version 9.5p1.

Full release notes are at https://www.openssh.com/txt/release-9.5[].

gitref:676824f5cdf9[repository=src] (Sponsored by The FreeBSD Foundation)

The man:scp[1] utility now defaults to the SFTP protocol by default rather than the legacy scp/rcp protocol.

The man:scp[1] utility now defaults to the SFTP protocol, rather than the legacy scp/rcp protocol.

grahamperrinUnsubmitted

Done

gitref:676824f5cdf9[repository=src] (Sponsored by The FreeBSD Foundation)

- The man:scp[1] utility now defaults to the SFTP protocol by default, rather than the legacy scp/rcp protocol.

+ The man:scp[1] utility now defaults to the SFTP protocol, rather than the legacy scp/rcp protocol.

This removes the need for double-quoting wildcard expansion characters.

grahamperrin:

This removes the need for double-quoting wildcard expansion characters.

gitref:fb5aabcb990b[repository=src] (Sponsored by The FreeBSD Foundation)

RSA/SHA-1 signatures are now disabled by default in man:ssh[1].

It is possible to enable them on a per-host basis in a user's [.filename]#~/.ssh/config# file.

gitref:8c22023ca5e1[repository=src] (Sponsored by The FreeBSD Foundation)

The `VerifyHostKeyDNS` option for man:ssh[1] now defaults to `no`,

The `VerifyHostKeyDNS` option for man:ssh[1] now defaults to `no`, following the OpenSSH distribution.

following the OpenSSH distribution.

The `X11Forwarding` option also defaults to `no`.

gitref:41ff5ea22cb9[repository=src] gitref:77934b7a1301[repository=src] (Sponsored by The FreeBSD Foundation)

HPN option handling has been removed from OpenSSH.

HPN support was deprecated long ago, but the configuration options were still accepted (and ignored) for backwards compatibility.

gitref:348bea10b6f2[repository=src] (Sponsored by The FreeBSD Foundation)

The `VersionAddendum` option has been removed from the man:ssh[1] client.

gitref:bffe60ead024[repository=src] (Sponsored by The FreeBSD Foundation)

OpenSSL has been upgraded to version 3.0.11.

This is a major upgrade from version 1.1.1, which is nearing its end of life.

This is a major upgrade from version 1.1.1, which has reached its end of life.

Many components of the base system use a backward-compatible API, but will be migrated later.

gitref:aa7957345732[repository=src] gitref:b077aed33b7b[repository=src] (Sponsored by The FreeBSD Foundation)

`xz` has been upgraded to version 5.4.3.

`zlib` has been upgraded to version 1.3.

`zstd` has been upgraded to version 1.5.2.

(Sponsored by Klara, Inc)

[[userland-deprecated-programs]]

=== Deprecated Applications

man:mergemaster[8] has been deprecated.

Its replacement is man:etcupdate[8].

gitref:398b12691b4f[repository=src] (Sponsored by The FreeBSD Foundation)

[[userland-libraries]]

=== Runtime Libraries and API

The `libncursesw` library (see man:ncurses[3X]) has been split into `libtinfow` and `libncursesw`.

Linker scripts should make this transparent for consumers.

`pkg-config` files are now installed to ease ports detecting the `ncurses` setup from base.

man:pkg-config[8] files are now installed, to ease ports detecting the `ncurses` setup from base.

gitref:396851c20aeb[repository=src]

The prototype of man:qsort_r[3] has been modified to match POSIX, which adopted the glibc-based interface.

gitref:af3c78886fd8[repository=src]

The `COMPAT_LIB32` build option has been implemented for aarch64 (arm64) and is enabled by default.

This provides armv7 32-bit-compatible libraries and header files for arm64 systems for building and running most armv7 32-bit binaries.

gitref:f1d5183124d3[repository=src] gitref:d5d97bed4ab6[repository=src] gitref:a1b675731301[repository=src]

Show All 29 Lines

The `acpi_timer_test` is disabled by default, forcing the use of ACPI-fast rather than ACPI-safe, and speeding the boot process.

The broken-ACPI-timers workaround can be re-enabled by setting the `hw.acpi.timer_test_enabled=1` tunable.

If timekeeping issues are observed, please test with `hw.acpi.timer_test_enabled=1` in man:loader.conf[8] and report if that fixes the problem.

gitref:a8b89dff6ac0[repository=src]

The introduction to the kernel internals manual pages, man:intro[9], has been rewritten and improved.

gitref:84f9f2c5cf78[repository=src] (Sponsored by The FreeBSD Foundation)

Boottrace is a new kernel-userspace interface for capturing trace events during system boot and shutdown.

man:boottrace[4] is a new kernel-userspace interface for capturing trace events during system boot and shutdown.

Event annotations are present in the boot and shutdown paths in the kernel; system utilities (man:init[8], man:shutdown[8], man:reboot[8]); and man:rc[8] scripts (via man:boottrace[8]).

Boottrace focuses on the ease of use and is aimed primarily at system administrators.

`boottrace` focuses on ease of use and is aimed primarily at system administrators.

It is available in the default `GENERIC` kernel and can be enabled by toggling a single man:sysctl[8] variable.

It is available in the default `GENERIC` kernel and can be enabled by toggling a man:sysctl[8] variable.

See man:boottrace[4] for more details.

gitref:da5b7e90e740[repository=src] gitref:5a8fceb3bd9f[repository=src] gitref:7b0a665d72c0[repository=src] gitref:13ec1e3155c7[repository=src] gitref:318d0db5fe8a[repository=src] gitref:1ae2c59bcf21[repository=src] (Sponsored by NetApp, Inc.) (Sponsored by Klara, Inc)

FreeBSD can now run inside the Firecracker VMM via the amd64 `FIRECRACKER` kernel configuration.

gitref:469ad8603127[repository=src] (Sponsored by https://www.patreon.com/cperciva[])

FreeBSD now reboots faster.

The `kern.reboot_wait_time` sysctl has been added to control the delay before rebooting after printing all kernel messages on the console.

Show All 37 Lines

It can be set with man:kbdcontrol[1] again.

There is integration with man:devd[8] for people wishing to use their sound cards for the beep.

gitref:ba48d52ca6c8[repository=src] gitref:4ac3d08a9693[repository=src] gitref:2533eca1c2b9[repository=src] (Sponsored by Netflix)

When using the default man:vt[4] console, the audible bell is no longer enabled by default.

It can be enabled with these commands: `sysctl kern.vt.enable_bell=1` and `kbdcontrol -b normal`.

gitref:225639e7db68[repository=src]

Improvements have been made in DPAA2 (second generation Data Path Acceleration Architecture – a hardware-level networking architecture found in some NXP SoCs).

Improvements have been made in DPAA2 (second generation Data Path Acceleration Architecture -- a hardware-level networking architecture found in some NXP SoCs).

It runs NXP-supplied firmware which provides DPAA2 objects as an abstraction layer, and provides a `dpni` network interface.

Separation between DPAA2 channels has been improved significantly in order to isolate access to the DMA resources and cleanup operations, and avoid kernel panics under heavy network load (1 Gbit/s links).

Other improvements include FDT/ACPI MDIO support, netboot over DPAA2 and separate command portals (DPMCP) support.

Drivers for ISA sound cards have been removed.

gitref:92e6b4712b53[repository=src] gitref:df51e63eb5d7[repository=src] gitref:aa83e9b189d6[repository=src] gitref:754decef384a[repository=src] gitref:5126e5eeeb5e[repository=src] gitref:716924cb4832[repository=src] gitref:9054e296819f[repository=src] (Sponsored by The FreeBSD Foundation)

The AHB bus front end has been removed from man:ath[4], as it was used only by MIPS.

gitref:37c8ee8847fa[repository=src]

A fix has been implemented for frame buffer addressing that affects framebuffers mapped above 4 GB physical on i386 and Book-E powerpc.

A fix has been implemented for frame buffer addressing that affects frame buffers mapped above 4 GB physical on i386 and Book-E powerpc.

gitref:a78bb831a17f[repository=src]

//XXX this was in 13.2; remove/place in MERGED section?

The man:igc[4] driver for the Intel I225 Ethernet controller is included, supporting 2.5 Gbps operation.

gitref:517904de5cca[repository=src] (Sponsored by Rubicon Communications, LLC ("Netgate"))

The man:iwlwifi[4] driver for Intel wireless interfaces has been updated to the latest version, supporting chipsets up to WiFi 6E AX411/AX211/AX210, and with preparations for upcoming BX and SC chipsets.

(Sponsored by The FreeBSD Foundation)

The man:rtw88[4] driver for Realtek wireless PCI interfaces has been updated.

There have been stability fixes and enhancements to the KPI to support Linux device drivers, along with the net80211 layer for wireless drivers.

(Sponsored by The FreeBSD Foundation)

The Microsoft Azure Network Adapter(MANA) VF (virtual function) is now supported.

The Microsoft Azure Network Adapter (MANA) VF (virtual function) is now supported.

gitref:ce110ea12fce[repository=src] (Sponsored by Microsoft)

NVME disks are now `nda` devices by default, for example `nda0`; see man:nda[4].

NVMe disks are now `nda` devices by default, for example `nda0`; see man:nda[4].

Symbolic links for the previous man:nvd[4] device names are created in `/dev`.

Symbolic links for the previous man:nvd[4] device names are created in [.filename]#/dev#.

However, configuration such as man:fstab[5] should be updated to refer to the new device names.

Options to control the use of `nda` devices and symbolic links are described in man:nda[4].

gitref:bdc81eeda05d[repository=src] (Sponsored by Netflix)

The man:pms[4] driver, `pmspcv`, has been removed from the `GENERIC` kernel configurations for x86, as it was large and uncommonly used.

It can be loaded as a module by placing `pmspcv_load="YES"` in man:loader.conf[5].

gitref:95e4f5ef7cce[repository=src] (Sponsored by Rubicon Communications, LLC ("Netgate"))

Show All 34 Lines

[[storage]]

== Storage

This section covers changes and additions to file systems and other storage subsystems, both local and networked.

[[storage-general]]

=== General Storage

man:gconcat[8] and its kernel support now have the ability to append devices to the concatenated device that were not present at creation time.

man:gconcat[8] and its kernel support now have the ability to append devices to the concatenated device that were not present when the gconcat device was created.

gitref:d575e81fbcfa[repository=src]

A new man:gunion[8] utility tracks changes to a read-only disk on a writable disk.

This can be useful for making tentative changes to the disk, such as file system repairs or software upgrades, and then either committing or reverting them.

gitref:c7996ddf8000[repository=src]

[[storage-nfs]]

=== NFS Changes

▲ Show 20 Lines • Show All 50 Lines • ▼ Show 20 Lines

* fully adaptive ARC, a unified ARC that minimizes the need for manual tuning

* zstd early abort, improving efficiency with uncompressible data

* I/O prefetch improvements

* general optimization.

ZFS has been enabled on 32-bit `powerpc`/`powerpcspe`.

gitref:63715498ac6b[repository=src]

[[boot-loader]]

=== Boot Loader Changes

[[boot]]

== Boot Loader Changes

== Boot Changes

This section covers the boot loader, boot menu, and other boot-related changes.

The lua-flavored man:loader[8] will now interpret `.lua` files that appear in `loader_conf_files` as lua, and execute them in a sandbox.

[[boot-loader]]

=== Boot Loader Changes

The lua-flavored man:loader[8] will now interpret [.filename]#.lua# files that appear in `loader_conf_files` as lua, and execute them in a sandbox.

Existing loader environment variables are available as globals in the sandbox, and any global variable set, if not a table value, will be reflected in the loader environment upon successful execution of the configuration file.

Environment variables with names that aren't valid lua names may be accessed as indices of `_ENV`; e.g., `_ENV['net.fibs']`.

gitref:3cb2f5f369ec[repository=src]

EC2 instances now boot using UEFI where available, substantially speeding the boot process.

gitref:b43d7aa09b3c[repository=src] gitref:bcf9147144f3[repository=src] (Sponsored by https://www.patreon.com/cperciva[])

[[network]]

▲ Show 20 Lines • Show All 54 Lines • ▼ Show 20 Lines

IPv4 was changed not to broadcast the lowest address on a subnet (host 0) unless it is configured as the broadcast address.

This allows the lowest address on a subnet to be used for a host.

gitref:fd0765933c3c[repository=src]

[[hardware]]

== Hardware Support

This section covers general hardware support for physical machines, hypervisors, and virtualization environments, as well as hardware changes and updates that do not otherwise fit in other sections of this document.

This section covers general hardware support for physical machines, hypervisors, and virtualization environments, as well as hardware changes and updates that do not fit in other sections of this document.

[[hardware-virtualization]]

=== Virtualization Support

[[ports]]

== Ports Collection and Package Infrastructure

This section covers changes to the FreeBSD Ports Collection, package infrastructure, and package maintenance and installation tools.

[[ports-packages]]

=== Packaging Changes

[[future-releases]]

== General Notes Regarding Future FreeBSD Releases

FreeBSD 15.0 is not expected to include support for 32-bit platforms.

However, 64-bit systems will still be able to run older 32-bit binaries.

Support for executing 32-bit binaries on 64-bit platforms via the `COMPAT_FREEBSD32` option will remain supported for at least the stable/15 and stable/16 branches.

Support for executing 32-bit binaries on 64-bit platforms via the `COMPAT_FREEBSD32` option will continue for at least the stable/15 and stable/16 branches.

Support for compiling individual 32-bit applications via `cc -m32` will also be supported for at least the stable/15 branch, which includes suitable headers in [.filename]#/usr/include# and libraries in [.filename]#/usr/lib32#.

Support for compiling individual 32-bit applications via `cc -m32` will also continue for at least the stable/15 branch, which includes suitable headers in [.filename]#/usr/include# and libraries in [.filename]#/usr/lib32#.

grahamperrinUnsubmitted

Done

However, 64-bit systems will still be able to run older 32-bit binaries.

- Support for executing 32-bit binaries on 64-bit platforms via the `COMPAT_FREEBSD32` option will remain supported for at least the stable/15 and stable/16 branches.

- Support for compiling individual 32-bit applications via `cc -m32` will also be supported for at least the stable/15 branch, which includes suitable headers in [.filename]#/usr/include# and libraries in [.filename]#/usr/lib32#.

+ Support for executing 32-bit binaries on 64-bit platforms via the `COMPAT_FREEBSD32` option will continue for at least the stable/15 and stable/16 branches.

+ Support for compiling individual 32-bit applications via `cc -m32` will also continue for at least the stable/15 branch, which includes suitable headers in [.filename]#/usr/include# and libraries in [.filename]#/usr/lib32#.

Support for 32-bit platforms in ports for FreeBSD 15.0 and later releases is also deprecated, and these future releases may not include binary packages for 32-bit platforms or support for building 32-bit applications from ports.

In these two sentences, I'm not sure about this:

Support … will remain/be supported

If someone asked me, "Graham, are you supporting the support for x?", I'd think it peculiar.

grahamperrin: In these two sentences, I'm not sure about this: > Support … will remain/be supported If…

The FreeBSD stable/14 and earlier branches will retain existing 32-bit kernel and world support.

Ports will retain existing support for building ports and packages for 32-bit systems on stable/14 and earlier branches as long as those branches are supported by the ports system.

However, all 32-bit platforms are Tier-2 or Tier-3, and support for individual ports should be expected to degrade as upstreams deprecate 32-bit platforms.

With the current support schedule, stable/14 will be reach End of Life (EOL) 5 years after the release of FreeBSD {releaseCurrent}.

With the current support schedule, stable/14 will reach end of life (EOL) 5 years after the release of FreeBSD {releaseCurrent}.

The EOL of stable/14 would mark the end of support for 32-bit platforms including source releases, pre-built packages, and support for building applications from ports.

The EOL of stable/14 would mark the end of support for 32-bit platforms, including source releases, pre-built packages, and support for building applications from ports.

Given an estimated release date of October 2023 for {releaseCurrent}, support for 32-bit platforms would end in October 2028.

Given an estimated release date of November 2023 for {releaseCurrent}, support for 32-bit platforms would end in November 2028.

The project may choose to alter this approach when FreeBSD 15.0 is released by extending some level of 32-bit support for one or more platforms in 15.0 or later.

Users should use the FreeBSD {releaseCurrent} and following releases or the stable/14 branch to migrate off of 32-bit platforms.

Use FreeBSD {releaseCurrent} and following releases, or the stable/14 branch, to migrate off 32-bit platforms.

grahamperrinUnsubmitted

Not Done

The project may choose to alter this approach when FreeBSD 15.0 is released by extending some level of 32-bit support for one or more platforms in 15.0 or later.

- Use FreeBSD {releaseCurrent} and following releases or the stable/14 branch to migrate off 32-bit platforms.

+ Use FreeBSD {releaseCurrent} and following releases, or the stable/14, branch to migrate off 32-bit platforms.

grahamperrin:

grahamperrinUnsubmitted

Done

Sorry, comma in the wrong place. I meant:

Use FreeBSD {releaseCurrent} and following releases, or the stable/14 branch, to migrate off 32-bit platforms.

grahamperrin: Sorry, comma in the wrong place. I meant: > Use FreeBSD {releaseCurrent} and following…