![]() ![]() # List of Anaconda DBus modules that are not allowed to run. # List of Anaconda DBus modules that can be activated. # This option is deprecated and will be removed in the future. The following configuration file describes the default configuration of RHEL 9: You can modify the configuration of the product configuration files from /etc/anaconda/product.d/ and the custom configuration files from /etc/anaconda/conf.d/. The file provides a full default configuration of the installer. The default configuration file, located at /etc/anaconda/nf, contains the documented sections and options that are supported. The resulting configuration file is processed with the configparser configuration file parser. Each section is defined by a header, the comments starting with a # character and the keys to define the options. The Anaconda configuration file consists of sections, options and comments. You can write the Anaconda configuration files in the. Once you do so, follow the instructions in Section 2.2, “Creating a product.img File” to create your own product.img with custom graphics, and then Section 2.3, “Creating Custom Boot Images” to create a new bootable ISO image with your changes included.Ĥ.3.1. Configuring the default configuration files You could also change the background-repeat parameters to tile the background, or, if you are confident that every system you will be installing on will have the same display resolution, you can use background images which fill the entire bar.Īny of the files listed above can be customized. Therefore, the background images "fade" into the background color, which means that the backgrounds work on all resolutions without a need for image scaling. Instead, the backgrounds have a transparent background, and the stylesheet defines a matching background color on the line. The PNG image backgrounds do not scale, they are always displayed in their true dimensions. The most important part of the CSS file is the way in which it handles scaling based on resolution. */īackground-color: url('/usr/share/anaconda/pixmaps/topbar-bg.png') * This is a placeholder to be filled by a product-specific logo. * theme colors/images product_bg_color logo and sidebar classes */īackground-image: url('/usr/share/anaconda/pixmaps/sidebar-bg.png') īackground-image: url('/usr/share/anaconda/pixmaps/sidebar-logo.png') Completing post customization tasks"Ĭollapse section "6. Deploying and testing an Anaconda add-onĮxpand section "6. Using NormalTUISpoke to Define a Text Interface Spokeĥ.15. Adding support for the Add-on graphical user interface (GUI)ĥ.14. Anaconda services and configuration filesĥ.10. Communication across Anaconda threadsĥ.8. Developing installer add-ons"Ĭollapse section "5. Configuring the custom configuration filesĮxpand section "5. Configuring the product configuration filesĤ.3.3. Configuring the default configuration filesĤ.3.2. Customizing the Default Configuration"Ĥ.3.1. Customizing the Default Configuration"Ĭollapse section "4.3. ![]() Customizing the Default ConfigurationĮxpand section "4.3. Branding and chroming the graphical user interface"Ĥ.3. Branding and chroming the graphical user interface"Ĭollapse section "4. Branding and chroming the graphical user interfaceĮxpand section "4. Customizing the boot menu"Ĭollapse section "3. Extracting Red Hat Enterprise Linux boot imagesĮxpand section "3. Performing the pre-customization tasks"Ģ.3. Performing the pre-customization tasks"Ĭollapse section "2. Performing the pre-customization tasksĮxpand section "2. Introduction to Anaconda customization"ġ.1. Introduction to Anaconda customization"Ĭollapse section "1. Introduction to Anaconda customizationĮxpand section "1. Providing feedback on Red Hat documentationġ. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |