Fedora Considers Ending BIOS Boot Support

Fedora Developers are discussing the issue of stopping booting using the classic BIOS and leaving the installation option only on systems with UEFI support. It is noted that systems based on the Intel platform since 2005 come with UEFI and until 2020, Intel planned stop BIOS support in client systems and platforms for data centers.

Discussion of deprecating BIOS support in Fedora is also due to implementation simplification Technology selective display of the boot menu, in which the menu is hidden by default and is shown only after a crash or activation of an option in GNOME. For UEFI, the necessary functionality is already available in sd-boot, but when using the BIOS, it requires the application of patches for GRUB2.

In the discussion, some developers expressed disagreement with the removal of BIOS support, as the price of the optimization would be to stop the ability to use new releases of Fedora on some laptops and PCs released before 2013 and shipped with graphics cards without a UEFI-compatible vBIOS. It also mentions the need to boot Fedora on BIOS-only virtualization systems.

Other changes being discussed for implementation in Fedora 33 include:

  • Using The default file system is Btrfs on desktop and laptop editions of Fedora. Application
    The built-in Btrfs partition manager will solve problems with running out of free disk space when mounting the / and / home directories separately. With Btrfs, these partitions can be placed in two subpartitions, mounted separately, but using the same disk space. Btrfs will also allow features such as snapshots, transparent data compression, correct I/O isolation via cgroups2, and on-the-fly resizing of partitions.

  • Planned add background process SID (Storage Instantiation Daemon) for monitoring the status of devices in various storage subsystems (LVM, multipath, MD) and calling handlers when certain events occur, for example, to activate and deactivate devices. SID works on top of udev and responds to events from it, allowing you to get rid of the creation of complicated udev rules for interacting with various classes of devices and storage subsystems that are difficult to maintain and debug.

Source: opennet.ru

Add a comment