ArcoLinux Beta 24.05

Calamares

The effort to support multiple bootloaders—Grub, systemd-boot, and rEFInd—on the ArcoLinux project involved a detailed and critical review of the Calamares installer’s configuration. Using the latest code as of April 1, 2024, the team managed to streamline the boot process. Specifically, they achieved a significant reduction in boot time (by 10 seconds) when booting from the ISO. This improvement was realized by optimizing the handling of the Nvidia driver installation, opting to remove it mid-installation rather than before the desktop environment loads. Such a change suggests a strategic shift in the installation process, prioritizing a quicker transition to the user’s desktop.

The ArcoLinux project has seen substantial growth, incorporating a wide variety of applications, modules, settings, and scripts. This expansion has necessitated a reevaluation and reorganization of the configuration files and settings to maintain clarity and efficiency. The complexity and scale of the project underscore the importance of transparency and orderliness in its configurations to ensure that it remains manageable, customizable, and user-friendly.

This initiative demonstrates ArcoLinux’s commitment to improving user experience, system efficiency, and the adaptability of its distributions. By focusing on the intricacies of the installation process and the system’s initial load time, the team not only enhances the practical performance of the distribution but also showcases its dedication to addressing the technical challenges associated with supporting a wide range of hardware and user preferences.

This is also for the ArcoLinuxD users who have the arcolinuxd-system-config-git package.

CHOICE ON THE 1st OF MAY ISOS

Timeline – mid April we remove the hooks from the arcolinux(d)-system-config package leaving you exposed to possible bootloader issues IF you did not install the correct new package

Introduction:

ArcoLinux is taking significant strides towards enhancing the flexibility and user control over its bootloader configurations. In a recent update, the ArcoLinux team announced a series of changes aimed at improving the installation and booting process. These adjustments come with a focus on providing users with the ability to choose and switch between different bootloader options, specifically GRUB, systemd-boot, and the soon-to-be-available Refind. This article aims to dissect these updates, explaining their implications and how users can navigate through them.

Key Changes and Their Implications:

1. Install Refind Button NOT in April ISOs: The upcoming April release of ArcoLinux ISOs will NOT have the ‘Install Refind’ button. The Mays will have this bootloader option. We need to set the stage for the broader bootloader customization options to be introduced in May.
2. Splitting Pacman Hooks: A critical component of this transition involves the moving of Pacman hooks into three separate entities. This division allows for a more targeted application of these hooks based on the bootloader choice—GRUB, systemd-boot, or Refind. Each set of hooks is designed to ensure the smooth operation and reliability of its corresponding bootloader.
3. Enhanced Bootloader Flexibility: Starting May, users will have the option to switch between GRUB, systemd-boot, and Refind seamlessly. This flexibility, however, comes with a cautionary note. The ArcoLinux team emphasizes the importance of understanding your system’s setup before making any changes. Switching bootloaders without a clear understanding of your system’s configuration could lead to complications.
4. The Importance of Pacman Hooks: Pacman hooks play a pivotal role in maintaining system stability, especially during updates that affect the bootloader. By automating critical processes such as rebuilding the GRUB configuration, these hooks prevent potential boot issues. The upcoming changes aim to retain this safety mechanism while allowing for greater customization.

How to Navigate the Changes:

• Understanding Your Current Bootloader: Before considering any changes, users should determine their current bootloader configuration. Knowing whether your system uses GRUB or systemd-boot is crucial for a smooth transition.
• Preparing for the Transition: Users are encouraged to stay informed through ArcoLinux’s communication channels for updates and detailed instructions on how to adopt the new bootloader configurations. The phased implementation ensures users have ample time to understand and prepare for the changes.
• Safety and Precautions: While the flexibility to switch between bootloaders is a significant advancement, it comes with responsibilities. Users must acknowledge the disclaimer regarding potential system risks and ensure they have a clear understanding of their system’s architecture before making any changes.

Conclusion:

The forthcoming changes to ArcoLinux’s bootloader configuration represent a significant step towards giving users more control over their systems. By introducing the ability to choose and switch between different bootloaders, ArcoLinux is not only enhancing its system’s flexibility but also ensuring that safety mechanisms like Pacman hooks continue to protect users. As we approach these changes, it’s crucial for users to stay informed, understand their system’s configuration, and proceed with caution to make the most of these new options.

Timeline – mid April we remove the hooks from the arcolinux(d)-system-config package leaving you exposed to possible bootloader issues IF you did not install the correct new package