{"id":121485,"date":"2025-01-26T03:46:02","date_gmt":"2025-01-26T01:46:06","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/distributiv-opensuse-opublikoval-alternativnyj-installyator-agama-11"},"modified":"2025-01-26T03:46:02","modified_gmt":"2025-01-26T01:46:06","slug":"distributiv-opensuse-opublikoval-alternativnyj-installyator-agama-11","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/distributiv-opensuse-opublikoval-alternativnyj-installyator-agama-11","title":{"rendered":"The openSUSE distribution has released an alternative installer Agama 11","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The openSUSE project developers have introduced the Agama 11 installer, which is being developed to replace the traditional installation interface of SUSE and openSUSE, notably separating the user interface from the internal components of YaST. Agama supports various front-ends, such as a web interface for managing the installation. The code for the installer components is licensed under GPLv2 and is written in Ruby, Rust, and JavaScript\/TypeScript. <\/p>\n
The new installer can be tested in the alpha release of openSUSE 16 and the upcoming beta release of SUSE Linux Enterprise Server 16. Additionally, separate live builds for testing the new installer have been created for x86_64, ppc64le, s390x, and ARM64 architectures, supporting the installation of the alpha version of openSUSE Leap 16, continuously updated builds of openSUSE Tumbleweed and openSUSE Slowroll, as well as the MicroOS container-based edition. <\/p>\n
The goals of the Agama development include eliminating existing limitations of the graphical interface; expanding the functionality of YaST for use in other applications; moving away from a single programming language; and encouraging the creation of alternative configurations by community members. <\/p>\n
The installer provides features such as selecting an initial set of applications, configuring network connections, language settings, keyboard layout, time zone, and localization options, preparing storage devices, and partitioning, as well as adding users to the system. <\/p>\n
For installing packages, checking hardware, partitioning disks, and other necessary installation functions, Agama continues to use YaST libraries, on top of which are service wrappers that abstract access to the libraries via a unified communication protocol based on HTTP. The installer employs a multiprocess architecture that ensures the user interaction interface remains responsive while other tasks are executed. <\/p>\n
The basic interface for managing installations is built using web technologies. The web interface is written in JavaScript using the React framework and PatternFly components. The messaging service, along with a built-in HTTP server, is written in Ruby.
<\/center> <\/p>\n
In the new version: <\/p>\n
\n
After selecting the operating system type, a screen is now displayed for setting the root user password. Previously, the user had to separately navigate to the 'Users' section and return to the summary screen; now the root setup is integrated into the installation process offered by the installer.
<\/center>\n
The main screen displayed after setting the root password has been redesigned. The key change is the display of the Install button in all sections, allowing users to proceed to installation from any settings section.
<\/center>\n
If certain settings are missing to initiate the installation, a special indicator appears on the Install button, providing hints on the required actions.
<\/center>\n
For the commercial distribution of SUSE Linux Enterprise Server 16, registration steps have been implemented to gain access to repositories and confirm the license agreement.
<\/center>
<\/center>\n
In the command-line installation mode, which can be used from scripts or when the web interface is not available, an option '--api' has been implemented to manage the installation from another computer.\n
In the automatic installation mode, support for embedding scripts into the installation configuration has been added. A 'scripts' section has been proposed for adding scripts that run before or after installation, as well as during the first boot of the installed system.\n
In the configuration for the automatic installation mode, the capability for automatic generation of physical partitions in the LVM volume group based on the disk specified as the LVM foundation has been introduced. Additionally, support for defining a configuration for unlocking encrypted disks, the decryption information for which is stored in TPMv2, has been added. <\/ul>\n
![\"The](\"\/wp-content\/uploads\/2025\/01\/e110fbba6e16c35d7cf166c6007b8e14.png\")
<\/center> <\/p>\n![\"The](\"\/wp-content\/uploads\/2025\/01\/3be5d1244c8d1a18b12dec4ba5b4acca.png\")
<\/center>\n![\"The](\"\/wp-content\/uploads\/2025\/01\/53629b97b8566d6793f1353cf43eedc0.png\")
<\/center>\n![\"The](\"\/wp-content\/uploads\/2025\/01\/419b3d1d6d4cc083e4f127b8123e943e.png\")
<\/center>\n![\"The](\"\/wp-content\/uploads\/2025\/01\/688fe702b03a5ad839444601a23a27c7.png\")
<\/center> ![\"The](\"\/wp-content\/uploads\/2025\/01\/379192492bb190d6ba2b64a53be97ace.png\")
<\/center>\n