Fedora is considering the possibility of discontinuing BIOS support at boot time

Fedora developers are discussing The issue of discontinuing support for classic BIOS and allowing installation only on systems that support UEFI is noted. It is mentioned that Intel-based systems have shipped with UEFI since 2005, and until 2020, Intel planned will cease BIOS support in client systems and data center platforms.

The discussion on phasing out BIOS support in Fedora is also driven by the simplification of implementation. technologies selective display of the boot menu, where the menu is hidden by default and only shown after a failure or activation of an option in GNOME. The necessary functionality for UEFI is already available in sd-boot, but using BIOS requires patches for GRUB2.

In the discussion, some developers expressed disagreement with discontinuing BIOS support, as the cost of optimization will be the inability to use new Fedora releases on some laptops and PCs released before 2013 that come with graphics cards without UEFI-compatible vBIOS. It is also mentioned that Fedora needs to boot on virtualization systems that only support BIOS.

Among other changes being discussed for implementation in Fedora 33, the following can be noted:

• Using the default file system Btrfs in desktop and laptop editions of Fedora. The application of
  the built-in Btrfs partition manager will help solve issues with running out of free disk space when separately mounting the directories / and /home. With Btrfs, these partitions can be placed in two subvolumes that are mounted separately but use shared disk space. Btrfs will also allow the use of features such as snapshots, transparent data compression, proper isolation of input/output operations through cgroups2, and on-the-fly resizing of partitions.
• It is planned to add a background process SID (Storage Instantiation Daemon) for monitoring the status of devices across various storage subsystems (LVM, multipath, MD) and invoking handlers upon certain events, such as activating and deactivating devices. SID operates as an overlay on udev and responds to events from it, eliminating the need for complex udev rules to interact with various classes of devices and storage subsystems that are difficult to maintain and debug.

Source: opennet.ru