Documentation for a newer release is available. View Latest


Anaconda changes

This section covers changes in the Anaconda installer, including changes in the graphical and text mode interactive installers, Kickstart, and installer boot options.

General changes

  • /boot can now be placed on a BTRFS subvolume.

  • It is no longer possible to attempt to add more than the maximum allowed number of boot-device NVRAMs on ppc64le.

  • Anaconda now uses the DBus storage module instead of the local storage object. This change has been in development for multiple releases, and is now complete.

  • Anaconda add-ons now have full DBus support, allowing add-on developers to use their own DBus modules. See the add-on example for more information.

  • The Anaconda development team has implemented their own DBus library, python3-dasbus. The library is written in Python, based on GLib, and inspired by pydbus. The repository, including documentation, is available at GitHub.

  • Comps files can now set specific architectures on which packages can be installed.

  • Packages can no longer be downloaded to RAM. This option has been disabled because it could previously cause out-of-memory issues. Packages can now only be downloaded to a hard drive, which also means the minimum storage requirements are slightly higher.

  • The Network & Hostname screen no longer allows a trailing dot in a host name, which mirrors the behavior of the underlying systemd-hostnamed and the kernel. Previously, attempting to set such a host name crashed the installer. Note that the actual FQDN specification does technically allow for host names with a trailing dot, but the installer does not.

  • Translations have been migrated to the Weblate platform. See the project page if you would like to contribute.

Kickstart changes

  • The liveimg command now avoids attempts to download an image twice, which could previously cause the installer to crash due to running out of memory.

  • The %packages section now supports the --ignorebroken option. Using this option, you can stop DNF from checking packages, groups, or modules with conflicting files. The default behavior is to abort the installation with an error listing the conflicting files.