diff --git a/SOURCES/anaconda-user-help-almalinux-branding.patch b/SOURCES/anaconda-user-help-almalinux-branding.patch new file mode 100644 index 0000000..3bef8d5 --- /dev/null +++ b/SOURCES/anaconda-user-help-almalinux-branding.patch @@ -0,0 +1,983 @@ +diff -ruN anaconda-user-help-8.3.3.orig/rhel/anaconda-help-anchors.json anaconda-user-help-8.3.3/rhel/anaconda-help-anchors.json +--- anaconda-user-help-8.3.3.orig/rhel/anaconda-help-anchors.json 2020-09-03 18:22:37.000000000 -0700 ++++ anaconda-user-help-8.3.3/rhel/anaconda-help-anchors.json 2020-11-04 16:03:18.838000000 -0800 +@@ -33,7 +33,7 @@ + "connect-to-red-hat_configuring-software-settings", + + "ProgressHub": +-"installation-complete_installing-RHEL", ++"installation-complete_installing-ALMA", + + "RootPasswordSpoke": + "configuring-a-root-password_graphical-installation", +diff -ruN anaconda-user-help-8.3.3.orig/rhel/en-US/anaconda-help.xml anaconda-user-help-8.3.3/rhel/en-US/anaconda-help.xml +--- anaconda-user-help-8.3.3.orig/rhel/en-US/anaconda-help.xml 2020-09-03 18:22:37.000000000 -0700 ++++ anaconda-user-help-8.3.3/rhel/en-US/anaconda-help.xml 2020-11-04 16:00:14.792000000 -0800 +@@ -2,11 +2,11 @@ + + Customizing your installation + 2020-09-04 +-Red Hat ++AlmaLinux + + + +-<simpara>When installing Red Hat Enterprise Linux, you can customize location, software, and system settings and parameters, using the <emphasis role="strong">Installation Summary</emphasis> window.</simpara> ++<simpara>When installing AlmaLinux, you can customize location, software, and system settings and parameters, using the <emphasis role="strong">Installation Summary</emphasis> window.</simpara> + <simpara>The <emphasis role="strong">Installation Summary</emphasis> window contains the following categories:</simpara> + <itemizedlist> + <listitem> +@@ -16,7 +16,7 @@ + <simpara><emphasis role="strong">SOFTWARE</emphasis>: You can configure Installation Source and Software Selection.</simpara> + </listitem> + <listitem> +-<simpara><emphasis role="strong">SYSTEM</emphasis>: You can configure Installation Destination, Connect to Red Hat, KDUMP, Network and Host Name, and Security Policy.</simpara> ++<simpara><emphasis role="strong">SYSTEM</emphasis>: You can configure Installation Destination, KDUMP, Network and Host Name, and Security Policy.</simpara> + </listitem> + <listitem> + <simpara><emphasis role="strong">USER SETTINGS</emphasis>: You can configure a root password to log in to the administrator account that is used for system administration tasks, and create a user account to login to the system.</simpara> +@@ -40,7 +40,7 @@ + <row> + <entry align="left" valign="top"><simpara><emphasis role="strong">Warning symbol type 1</emphasis></simpara></entry> + <entry align="left" valign="top"><simpara>Yellow triangle with an exclamation mark and red text</simpara></entry> +-<entry align="left" valign="top"><simpara>Requires attention before installation. For example, Network & Host Name requires attention before you can register and download from the Content Delivery Network (CDN).</simpara></entry> ++<entry align="left" valign="top"><simpara>Requires attention before installation.</simpara></entry> + </row> + <row> + <entry align="left" valign="top"><simpara><emphasis role="strong">Warning symbol type 2</emphasis></simpara></entry> +@@ -53,12 +53,12 @@ + <note> + <simpara>A warning message is displayed at the bottom of the <emphasis role="strong">Installation Summary</emphasis> window and the <emphasis role="strong">Begin Installation</emphasis> button is disabled until you configure all of the required categories.</simpara> + </note> +-<simpara>This section contains information about customizing your Red Hat Enterprise Linux installation using the Graphical User Interface (GUI). The GUI is the preferred method of installing Red Hat Enterprise Linux when you boot the system from a CD, DVD, or USB flash drive, or from a network using PXE.</simpara> ++<simpara>This section contains information about customizing your AlmaLinux installation using the Graphical User Interface (GUI). The GUI is the preferred method of installing AlmaLinux when you boot the system from a CD, DVD, or USB flash drive, or from a network using PXE.</simpara> + <note> + <simpara>There may be some variance between the online help and the content that is published on the Customer Portal. For the latest updates, see the installation content on the Customer Portal.</simpara> + </note> + </preface> +-<chapter xml:id="installing-rhel-using-anaconda_graphical-installation"> ++<chapter xml:id="installing-alma-using-anaconda_graphical-installation"> + <title>Configuring language and location settings + The installation program uses the language that you selected during installation. + +@@ -76,18 +76,18 @@ + + Procedure + +-From the left-hand pane of the Welcome to Red Hat Enterprise Linux window, select a language. Alternatively, type your preferred language into the Search field. ++From the left-hand pane of the Welcome to AlmaLinux window, select a language. Alternatively, type your preferred language into the Search field. + + A language is pre-selected by default. If network access is configured, that is, if you booted from a network server instead of local media, the pre-selected language is determined by the automatic location detection feature of the GeoIP module. If you used the inst.lang= option on the boot command line or in your PXE server configuration, then the language that you define with the boot option is selected. + + + +-From the right-hand pane of the Welcome to Red Hat Enterprise Linux window, select a location specific to your region. ++From the right-hand pane of the Welcome to AlmaLinux window, select a location specific to your region. + + + Click Continue to proceed to the window. + +-If you are installing a pre-release version of Red Hat Enterprise Linux, a warning message is displayed about the pre-release status of the installation media. Click I want to proceed to continue with the installation, or I want to exit to quit the installation and reboot the system. ++If you are installing a pre-release version of AlmaLinux, a warning message is displayed about the pre-release status of the installation media. Click I want to proceed to continue with the installation, or I want to exit to quit the installation and reboot the system. + + + +@@ -105,13 +105,13 @@ +
+ Configuring keyboard, language, and time and date settings + +-Keyboard, Language, and Time and Date Settings are configured by default as part of . ++Keyboard, Language, and Time and Date Settings are configured by default as part of . + To change any of the settings, complete the following steps, otherwise proceed to . + + + Procedure: Configuring keyboard settings + +-From the Installation Summary window, click Keyboard. The default layout depends on the option selected in . ++From the Installation Summary window, click Keyboard. The default layout depends on the option selected in . + + + Click + to open the Add a Keyboard Layout window and change to a different layout. +@@ -156,8 +156,8 @@ + + From the Installation Summary window, click Time & Date. The Time & Date window opens. + +-The Time & Date settings are configured by default based on the settings you selected in . +-The list of cities and regions come from the Time Zone Database (tzdata) public domain that is maintained by the Internet Assigned Numbers Authority (IANA). Red Hat can not add cities or regions to this database. You can find more information at the IANA official website. ++The Time & Date settings are configured by default based on the settings you selected in . ++The list of cities and regions come from the Time Zone Database (tzdata) public domain that is maintained by the Internet Assigned Numbers Authority (IANA). AlmaLinux can not add cities or regions to this database. You can find more information at the IANA official website. + + + +@@ -191,9 +191,9 @@ + This section contains information about configuring Installation Destination, KDUMP, Network and Host Name, and Security Policy. +
+ Configuring installation destination +-Use the Installation Destination window to configure the storage options, for example, the disks that you want to use as the installation target for your Red Hat Enterprise Linux installation. You must select at least one disk. ++Use the Installation Destination window to configure the storage options, for example, the disks that you want to use as the installation target for your AlmaLinux installation. You must select at least one disk. + +-Back up your data if you plan to use a disk that already contains data. For example, if you want to shrink an existing Microsoft Windows partition and install Red Hat Enterprise Linux as a second system, or if you are upgrading a previous release of Red Hat Enterprise Linux. Manipulating partitions always carries a risk. For example, if the process is interrupted or fails for any reason data on the disk can be lost. ++Back up your data if you plan to use a disk that already contains data. For example, if you want to shrink an existing Microsoft Windows partition and install AlmaLinux as a second system, or if you are upgrading a previous release of AlmaLinux. Manipulating partitions always carries a risk. For example, if the process is interrupted or fails for any reason data on the disk can be lost. + + + +@@ -203,10 +203,10 @@ + If you choose to partition your system automatically, you should manually edit your /boot partition. + + +-To configure the Red Hat Enterprise Linux boot loader to chain load from a different boot loader, you must specify the boot drive manually by clicking the Full disk summary and bootloader link from the Installation Destination window. ++To configure the AlmaLinux boot loader to chain load from a different boot loader, you must specify the boot drive manually by clicking the Full disk summary and bootloader link from the Installation Destination window. + + +-When you install Red Hat Enterprise Linux on a system with both multipath and non-multipath storage devices, the automatic partitioning layout in the installation program creates volume groups that contain a mix of multipath and non-multipath devices. This defeats the purpose of multipath storage. It is recommended that you select either multipath or non-multipath devices on the Installation Destination window. Alternatively, proceed to manual partitioning. ++When you install AlmaLinux on a system with both multipath and non-multipath storage devices, the automatic partitioning layout in the installation program creates volume groups that contain a mix of multipath and non-multipath devices. This defeats the purpose of multipath storage. It is recommended that you select either multipath or non-multipath devices on the Installation Destination window. Alternatively, proceed to manual partitioning. + + + +@@ -222,7 +222,7 @@ + + From the Local Standard Disks section, select the storage device that you require; a white check mark indicates your selection. Disks without a white check mark are not used during the installation process; they are ignored if you choose automatic partitioning, and they are not available in manual partitioning. + +-All locally available storage devices (SATA, IDE and SCSI hard drives, USB flash and external disks) are displayed under Local Standard Disks. Any storage devices connected after the installation program has started are not detected. If you use a removable drive to install Red Hat Enterprise Linux, your system is unusable if you remove the device. ++All locally available storage devices (SATA, IDE and SCSI hard drives, USB flash and external disks) are displayed under Local Standard Disks. Any storage devices connected after the installation program has started are not detected. If you use a removable drive to install AlmaLinux, your system is unusable if you remove the device. + + + +@@ -252,7 +252,7 @@ + + + +-Optional: To reclaim space from an existing partitioning layout, select the I would like to make additional space available check box. For example, if a disk you want to use already contains a different operating system and you want to make this system’s partitions smaller to allow more room for Red Hat Enterprise Linux. ++Optional: To reclaim space from an existing partitioning layout, select the I would like to make additional space available check box. For example, if a disk you want to use already contains a different operating system and you want to make this system’s partitions smaller to allow more room for AlmaLinux. + + + Optional: Select Encrypt my data to encrypt all partitions except the ones needed to boot the system (such as /boot) using Linux Unified Key Setup (LUKS). Encrypting your hard drive is recommended. +@@ -266,7 +266,7 @@ + + Click Save Passphrase to complete disk encryption. + +-If you lose the LUKS passphrase, any encrypted partitions and their data is completely inaccessible. There is no way to recover a lost passphrase. However, if you perform a Kickstart installation, you can save encryption passphrases and create backup encryption passphrases during the installation. See the Performing an advanced RHEL installation document for information. ++ If you lose the LUKS passphrase, any encrypted partitions and their data is completely inaccessible. There is no way to recover a lost passphrase. However, if you perform a Kickstart installation, you can save encryption passphrases and create backup encryption passphrases during the installation. + + + +@@ -283,7 +283,7 @@ + Click Done. + + +-If you selected automatic partitioning and I would like to make additional space available, or if there is not enough free space on your selected hard drives to install Red Hat Enterprise Linux, the Reclaim Disk Space dialog box opens when you click Done, and lists all configured disk devices and all partitions on those devices. The dialog box displays information about how much space the system needs for a minimal installation and how much space you have reclaimed. ++If you selected automatic partitioning and I would like to make additional space available, or if there is not enough free space on your selected hard drives to install AlmaLinux, the Reclaim Disk Space dialog box opens when you click Done, and lists all configured disk devices and all partitions on those devices. The dialog box displays information about how much space the system needs for a minimal installation and how much space you have reclaimed. + + If you delete a partition, all data on that partition is lost. If you want to preserve your data, use the Shrink option, not the Delete option. + +@@ -294,7 +294,7 @@ + + To reclaim space, select a disk or partition, and click either the Delete button to delete that partition, or all partitions on a selected disk, or click Shrink to use free space on a partition while preserving the existing data. + +-Alternatively, you can click Delete all, this deletes all existing partitions on all disks and makes this space available to Red Hat Enterprise Linux. Existing data on all disks is lost. ++Alternatively, you can click Delete all, this deletes all existing partitions on all disks and makes this space available to AlmaLinux. Existing data on all disks is lost. + + + +@@ -308,13 +308,13 @@ + +
+ Configuring boot loader +-Red Hat Enterprise Linux uses GRand Unified Bootloader version 2 (GRUB2) as the boot loader for AMD64 and Intel 64, IBM Power Systems, and ARM. For IBM Z, the zipl boot loader is used. ++AlmaLinux uses GRand Unified Bootloader version 2 (GRUB2) as the boot loader for AMD64, Intel 64, and ARM. + The boot loader is the first program that runs when the system starts and is responsible for loading and transferring control to an operating system. GRUB2 can boot any compatible operating system (including Microsoft Windows) and can also use chain loading to transfer control to other boot loaders for unsupported operating systems. + + Installing GRUB2 may overwrite your existing boot loader. + +-If an operating system is already installed, the Red Hat Enterprise Linux installation program attempts to automatically detect and configure the boot loader to start the other operating system. If the boot loader is not detected, you can manually configure any additional operating systems after you finish the installation. +-If you are installing a Red Hat Enterprise Linux system with more than one disk, you might want to manually specify the disk where you want to install the boot loader. ++If an operating system is already installed, the AlmaLinux installation program attempts to automatically detect and configure the boot loader to start the other operating system. If the boot loader is not detected, you can manually configure any additional operating systems after you finish the installation. ++If you are installing a AlmaLinux system with more than one disk, you might want to manually specify the disk where you want to install the boot loader. + + Procedure + +@@ -358,7 +358,7 @@ + + + +-The amount of memory that you reserve is determined by your system architecture (AMD64 and Intel 64 have different requirements than IBM Power) as well as the total amount of system memory. In most cases, automatic reservation is satisfactory. ++The amount of memory that you reserve is determined by your system architecture as well as the total amount of system memory. In most cases, automatic reservation is satisfactory. + + + Additional settings, such as the location where kernel crash dumps will be saved, can only be configured after the installation using either the system-config-kdump graphical interface, or manually in the /etc/kdump.conf configuration file. +@@ -398,7 +398,7 @@ + + + +-There are several types of network device naming standards used to identify network devices with persistent names, for example, em1 and wl3sp0. For information about these standards, see the Configuring and managing networking document. ++ There are several types of network device naming standards used to identify network devices with persistent names, for example, em1 and wl3sp0. + + + The host name can be either a fully-qualified domain name (FQDN) in the format hostname.domainname, or a short host name with no domain name. Many networks have a Dynamic Host Configuration Protocol (DHCP) service that automatically supplies connected systems with a domain name. To allow the DHCP service to assign the domain name to this machine, specify only the short host name. The value localhost.localdomain means that no specific static host name for the target system is configured, and the actual host name of the installed system is configured during the processing of the network configuration, for example, by NetworkManager using DHCP or DNS. +@@ -453,7 +453,6 @@ + Editing network interface configuration + This section contains information about the most important settings for a typical wired connection used during installation. Configuration of other types of networks is broadly similar, although the specific configuration parameters might be different. + +-On IBM Z, you cannot add a new connection as the network subchannels need to be grouped and set online beforehand, and this is currently done only in the booting phase. + + + Procedure +@@ -479,7 +478,7 @@ + + + +-When enabled on a wired connection, the system automatically connects during startup or reboot. On a wireless connection, the interface attempts to connect to any known wireless networks in range. For further information about NetworkManager, including the nm-connection-editor tool, see the Configuring and managing networking document. ++When enabled on a wired connection, the system automatically connects during startup or reboot. On a wireless connection, the interface attempts to connect to any known wireless networks in range. + + + You can enable or disable all users on the system from connecting to this network using the All users may connect to this network option. If you disable this option, only root will be able to connect to this network. +@@ -551,21 +550,13 @@ + + +
+-
+-Additional resources +- +- +-To learn more about network configuration after installation, see the Configuring and managing networking document. +- +- +-
+
+
+ Configuring Security Policy +-This section contains information about the Red Hat Enterprise Linux 8.3 Beta security policy and how to configure it for use on your system. ++This section contains information about the AlmaLinux 8.3 security policy and how to configure it for use on your system. +
+ About security policy +-The Red Hat Enterprise Linux security policy adheres to restrictions and recommendations (compliance policies) defined by the Security Content Automation Protocol (SCAP) standard. The packages are automatically installed. However, by default, no policies are enforced and therefore no checks are performed during or after installation unless specifically configured. ++The AlmaLinux security policy adheres to restrictions and recommendations (compliance policies) defined by the Security Content Automation Protocol (SCAP) standard. The packages are automatically installed. However, by default, no policies are enforced and therefore no checks are performed during or after installation unless specifically configured. + Applying a security policy is not a mandatory feature of the installation program. If you apply a security policy to the system, it is installed using restrictions and recommendations defined in the profile that you selected. The openscap-scanner package is added to your package selection, providing a preinstalled tool for compliance and vulnerability scanning. After the installation finishes, the system is automatically scanned to verify compliance. The results of this scan are saved to the /root/openscap_data directory on the installed system. You can also load additional profiles from an HTTP, HTTPS, or FTP server. +
+
+@@ -619,366 +610,18 @@ + + scap-security-guide(8) - The manual page for the scap-security-guide project contains information about SCAP security profiles, including examples on how to utilize the provided benchmarks using the OpenSCAP utility. + +- +-Red Hat Enterprise Linux security compliance information is available in the Security hardening document. +- + +
+
+ + + Configuring software options +-This section contains information about configuring Red Hat Content Delivery Network (CDN), your installation source and software selection settings, and activating a repository. +-
+-Configuring Connect to Red Hat +-The Red Hat Content Delivery Network (CDN), available from cdn.redhat.com, is a geographically distributed series of static web servers that contain content and errata that is consumed by systems. The content can be consumed directly, such as using a system registered to Red Hat Subscription Management. The CDN is protected by x.509 certificate authentication to ensure that only valid users have access. When a system is registered to Red Hat Subscription Management, the attached subscriptions govern which subset of the CDN the system can access. +-Registering and installing RHEL from the CDN provides the following benefits: +- +- +-The CDN installation method supports the Boot ISO and the Binary DVD ISO image files. However, the use of the smaller Boot ISO image file is recommended as it consumes less space than the larger Binary DVD ISO image file. +- +- +-The CDN uses the latest packages resulting in a fully up-to-date system right after installation. There is no requirement to install package updates immediately after installation as is often the case when using the Binary DVD ISO image file. +- +- +-Integrated support for connecting to Red Hat Insights and enabling System Purpose. +- +- +-
+-Introduction to System Purpose +-System Purpose is an optional but recommended feature of the Red Hat Enterprise Linux installation. You use System Purpose to record the intended use of a Red Hat Enterprise Linux 8 system, and ensure that the entitlement server auto-attaches the most appropriate subscription to your system. +-Benefits include: +- +- +-In-depth system-level information for system administrators and business operations. +- +- +-Reduced overhead when determining why a system was procured and its intended purpose. +- +- +-Improved customer experience of Subscription Manager auto-attach as well as automated discovery and reconciliation of system usage. +- +- +-You can enter System Purpose data in one of the following ways: +- +- +-During image creation +- +- +-During a GUI installation when using Connect to Red Hat to register your system and attach your Red Hat subscription +- +- +-During a Kickstart installation when using Kickstart automation scripts +- +- +-After installation using the syspurpose command-line (CLI) tool +- +- +-To record the intended purpose of your system, you can configure the following components of System Purpose. The selected values are used by the entitlement server upon registration to attach the most suitable subscription for your system. +- +- +-Role +- +- +-Red Hat Enterprise Linux Server +- +- +-Red Hat Enterprise Linux Workstation +- +- +-Red Hat Enterprise Linux Compute Node +- +- +- +- +-Service Level Agreement +- +- +-Premium +- +- +-Standard +- +- +-Self-Support +- +- +- +- +-Usage +- +- +-Production +- +- +-Development/Test +- +- +-Disaster Recovery +- +- +- +- +- +-Additional resources +- +-For more information about Image Builder, see the Composing a customized RHEL system image document. +- +- +-For more information about Kickstart, see the Performing an advanced RHEL installation document. +- +- +-For more information about Subscription Manager, see the Using and Configuring Red Hat Subscription Manager document. +- +- +-
+-
+-Configuring Connect to Red Hat options +-Use the following procedure to configure the Connect to Red Hat options in the GUI. +- +-You can register to the CDN using either your Red Hat account or your activation key details. +- +- +-Procedure +- +-Click Account. +- +- +-Enter your Red Hat Customer Portal username and password details. +- +- +- +- +-Optional: Click Activation Key. +- +- +-Enter your organization ID and activation key. You can enter more than one activation key, separated by a comma, as long as the activation keys are registered to your subscription. +- +- +- +- +-Select the Set System Purpose check box. System Purpose enables the entitlement server to determine and automatically attach the most appropriate subscription to satisfy the intended use of your RHEL 8 system. +- +- +-Select the required Role, SLA, and Usage from the corresponding drop-down lists. +- +- +- +- +-The Connect to Red Hat Insights check box is enabled by default. Clear the check box if you do not want to connect to Red Hat Insights. +- +-Red Hat Insights is a Software-as-a-Service (SaaS) offering that provides continuous, in-depth analysis of registered Red Hat-based systems to proactively identify threats to security, performance and stability across physical, virtual and cloud environments, and container deployments. +- +- +- +-Optional: Expand Options. +- +- +-Select the Use HTTP proxy check box if your network environment only allows external Internet access or access to content servers through an HTTP proxy. Clear the Use HTTP proxy check box if an HTTP proxy is not used. +- +- +-If you are running Satellite Server or performing internal testing, select the Custom server URL and Custom base URL check boxes and enter the required details. +- +- +- +-The Custom server URL field does not require the HTTP protocol, for example nameofhost.com. However, the Custom base URL field requires the HTTP protocol. +- +- +-To change the Custom base URL after registration, you must unregister, provide the new details, and then re-register. +- +- +- +- +- +- +- +-Click Register to register the system. When the system is successfully registered and subscriptions are attached, the Connect to Red Hat window displays the attached subscription details. +- +-Depending on the amount of subscriptions, the registration and attachment process might take up to a minute to complete. +- +- +- +-Click Done to return to the Installation Summary window. +- +- +-A Registered message is displayed under Connect to Red Hat. +- +- +- +- +-
+-
+-Installation source repository after system registration +-The installation source repository used after system registration is dependent on how the system was booted. +- +- +-System booted from the Boot ISO or the Binary DVD ISO image file +- +-If you booted the RHEL installation using either the Boot ISO or the Binary DVD ISO image file with the default boot parameters, the installation program automatically switches the installation source repository to the CDN after registration. +- +- +- +-System booted with the inst.repo=<URL> boot parameter +- +-If you booted the RHEL installation with the inst.repo=<URL> boot parameter, the installation program does not automatically switch the installation source repository to the CDN after registration. If you want to use the CDN to install RHEL, you must manually switch the installation source repository to the CDN by selecting the Red Hat CDN option in the Installation Source window of the graphical installation. If you do not manually switch to the CDN, the installation program installs the packages from the repository specified on the kernel command line. +- +- +- +- +- +- +-You can switch the installation source repository to the CDN using the rhsm Kickstart command only if you do not specify an installation source using inst.repo= on the kernel command line or the url command in the Kickstart file. You must use inst.stage2=<URL> on the kernel command line to fetch the installation image, but not specify the installation source. +- +- +-An installation source URL specified using a boot option or included in a Kickstart file takes precedence over the CDN, even if the Kickstart file contains the rhsm command with valid credentials. The system is registered, but it is installed from the URL installation source. This ensures that earlier installation processes operate as normal. +- +- +- +-
+-
+-Verifying your system registration from the CDN +-Use this procedure to verify that your system is registered to the CDN using the GUI. +- +-You can only verify your registration from the CDN if you have not clicked the Begin Installation button from the Installation Summary window. Once the Begin Installation button is clicked, you cannot return to the Installation Summary window to verify your registration. +- +- +-Prerequisite +- +-You have completed the registration process as documented in the and Registered is displayed under Connect to Red Hat on the Installation Summary window. +- +- +- +-Procedure +- +-From the Installation Summary window, select Connect to Red Hat. +- +- +-The window opens and displays a registration summary: +- +- +-Method +- +-The registered account name or activation keys are displayed. +- +- +- +-System Purpose +- +-If set, the role, SLA, and usage details are displayed. +- +- +- +-Insights +- +-If enabled, the Insights details are displayed. +- +- +- +-Number of subscriptions +- +-The number of subscriptions attached are displayed. +- +- +- +- +- +-Verify that the registration summary matches the details that were entered. +- +- +-
+-
+-Unregistering your system from the CDN +-Use this procedure to unregister your system from the CDN using the GUI. +- +- +- +-You can unregister from the CDN if you have not clicked the Begin Installation button from the Installation Summary window. Once the Begin Installation button is clicked, you cannot return to the Installation Summary window to unregister your registration. +- +- +-When unregistering, the installation program switches to the first available repository, in the following order: +- +- +-The URL used in the inst.repo=<URL> boot parameter on the kernel command line. +- +- +-An automatically detected repository on the installation media (USB or DVD). +- +- +- +- +- +- +-Prerequisite +- +-You have completed the registration process as documented in the and Registered is displayed under Connect to Red Hat on the Installation Summary window. +- +- +- +-Procedure +- +-From the Installation Summary window, select Connect to Red Hat. +- +- +-The Connect to Red Hat window opens and displays a registration summary: +- +- +-Method +- +-The registered account name or activation keys used are displayed. +- +- +- +-System Purpose +- +-If set, the role, SLA, and usage details are displayed. +- +- +- +-Insights +- +-If enabled, the Insights details are displayed. +- +- +- +-Number of subscriptions +- +-The number of subscriptions attached are displayed. +- +- +- +- +- +-Click Unregister to remove the registration from the CDN. The original registration details are displayed with a Not registered message displayed in the lower-middle part of the window. +- +- +-Click Done to return to the Installation Summary window. +- +- +-Connect to Red Hat displays a Not registered message, and Software Selection displays a Red Hat CDN requires registration message. +- +- +- +-After unregistering, it is possible to register your system again. Click Connect to Red Hat. The previously entered details are populated. Edit the original details, or update the fields based on the account, purpose, and connection. Click Register to complete. +- +- +-Related information +- +-For information about Red Hat Insights, see the Red Hat Insights product documentation. +- +- +-For information about Activation Keys, see the Understanding Activation Keys chapter of the Using Red Hat Subscription Management document. +- +- +-For information about how to set up an HTTP proxy for Subscription Manager, see the Using an HTTP proxy chapter of the Using and Configuring Red Hat Subscription Manager document. +- +- +-
+-
++This section contains information about configuring your installation source and software selection settings, and activating a repository. +
+ Configuring installation source +-Complete the steps in this procedure to configure an installation source from either auto-detected installation media, Red Hat CDN, or the network. ++Complete the steps in this procedure to configure an installation source from either auto-detected installation media or the network. + +-When the Installation Summary window first opens, the installation program attempts to configure an installation source based on the type of media that was used to boot the system. The full Red Hat Enterprise Linux Server DVD configures the source as local media. ++When the Installation Summary window first opens, the installation program attempts to configure an installation source based on the type of media that was used to boot the system. The full AlmaLinux DVD configures the source as local media. + + + Prerequisites +@@ -1011,7 +654,7 @@ + No additional configuration is necessary as the BaseOS and AppStream repositories are installed as part of the full installation image. + + +-Do not disable the AppStream repository check box if you want a full Red Hat Enterprise Linux 8 installation. ++Do not disable the AppStream repository check box if you want a full AlmaLinux 8 installation. + + + +@@ -1019,9 +662,6 @@ + + + +-Optional: Select the Red Hat CDN option to register your system, attach RHEL subscriptions, and install RHEL from the Red Hat Content Delivery Network (CDN). For more information, see the Registering and installing RHEL from the CDN section. +- +- + Optional: Select the On the network option to download and install packages from a network location instead of local media. + + +@@ -1102,15 +742,14 @@ + + + Use a predefined environment and additional software to customize your system. However, in a standard installation, you cannot select individual packages to install. To view the packages contained in a specific environment, see the repository/repodata/*-comps-repository.architecture.xml file on your installation source media (DVD, CD, USB). The XML file contains details of the packages installed as part of a base environment. Available environments are marked by the <environment> tag, and additional software packages are marked by the <group> tag. +-If you are unsure about which packages to install, Red Hat recommends that you select the Minimal Install base environment. Minimal install installs a basic version of Red Hat Enterprise Linux with only a minimal amount of additional software. After the system finishes installing and you log in for the first time, you can use the Yum package manager to install additional software. +-For more information about Yum package manager, see the Configuring basic system settings document. ++If you are unsure about which packages to install, AlmaLinux recommends that you select the Minimal Install base environment. Minimal install installs a basic version of AlmaLinux with only a minimal amount of additional software. After the system finishes installing and you log in for the first time, you can use the Yum package manager to install additional software. + + + +-The yum group list command lists all package groups from yum repositories. See the Configuring basic system settings document for more information. ++The yum group list command lists all package groups from yum repositories. + + +-If you need to control which packages are installed, you can use a Kickstart file and define the packages in the %packages section. See the Performing an advanced RHEL installation document for information about installing Red Hat Enterprise Linux using Kickstart. ++If you need to control which packages are installed, you can use a Kickstart file and define the packages in the %packages section. + + + +@@ -1146,13 +785,10 @@ + +
+ ++ + + Configuring storage devices +-You can install Red Hat Enterprise Linux on a large variety of storage devices. You can configure basic, locally accessible, storage devices in the Installation Destination window. Basic storage devices directly connected to the local system, such as hard disk drives and solid-state drives, are displayed in the Local Standard Disks section of the window. +-On IBM Z, this section contains activated Direct Access Storage Devices (DASDs). +- +-A known issue prevents DASDs configured as HyperPAV aliases from being automatically attached to the system after the installation is complete. These storage devices are available during the installation, but are not immediately accessible after you finish installing and reboot. To attach HyperPAV alias devices, add them manually to the /etc/dasd.conf configuration file of the system. +- ++You can install AlmaLinux on a large variety of storage devices. You can configure basic, locally accessible, storage devices in the Installation Destination window. Basic storage devices directly connected to the local system, such as hard disk drives and solid-state drives, are displayed in the Local Standard Disks section of the window. +
+ Storage device selection + The storage device selection window lists all storage devices that the installation program can access. Depending on your system and available hardware, some tabs might not be displayed. +@@ -1182,13 +818,7 @@ + + NVDIMM Devices + +-Under specific circumstances, Red Hat Enterprise Linux 8.3 Beta can boot and run from (NVDIMM) devices in sector mode on the Intel 64 and AMD64 architectures. +- +- +- +-System z Devices +- +-Storage devices, or Logical Units (LUNs), attached through the zSeries Linux FCP (Fiber Channel Protocol) driver. ++Under specific circumstances, AlmaLinux 8.3 can boot and run from (NVDIMM) devices in sector mode on the Intel 64 and AMD64 architectures. + + + +@@ -1220,7 +850,7 @@ + + + Select the check box to enable the device that you require during the installation process. +-Later in the installation process you can choose to install Red Hat Enterprise Linux on any of the selected devices, and you can choose to mount any of the other selected devices as part of the installed system automatically. ++Later in the installation process you can choose to install AlmaLinux on any of the selected devices, and you can choose to mount any of the other selected devices as part of the installed system automatically. + + + +@@ -1381,101 +1011,15 @@ + + +
+-
+-Configuring DASD storage devices +-Complete the following steps to configure DASD storage devices. +- +-Prerequisite +-The Installation Summary window is open. +- +- +-Procedure +- +-From the Installation Summary window, click Installation Destination. The Installation Destination window opens, listing all available drives. +- +- +-Under the Specialized & Network Disks section, click Add a disk…. The storage devices selection window opens. +- +- +-Click Add DASD. The Add DASD Storage Target dialog box opens and prompts you to specify a device number, such as 0.0.0204, and attach additional DASDs that were not detected when the installation started. +- +- +-Type the device number of the DASD that you want to attach in the Device number field. +- +- +-Click Start Discovery. +- +- +- +- +- +-If a DASD with the specified device number is found and if it is not already attached, the dialog box closes and the newly-discovered drives appear in the list of drives. You can then select the check boxes for the required devices and click Done. The new DASDs are available for selection, marked as DASD device 0.0.xxxx in the Local Standard Disks section of the Installation Destination window. +- +- +-If you entered an invalid device number, or if the DASD with the specified device number is already attached to the system, an error message appears in the dialog box, explaining the error and prompting you to try again with a different device number. +- +- +- +-
+-
+-Configuring FCP devices +-FCP devices enable IBM Z to use SCSI devices rather than, or in addition to, Direct Access Storage Device (DASD) devices. FCP devices provide a switched fabric topology that enables IBM Z systems to use SCSI LUNs as disk devices in addition to traditional DASD devices. +- +-Prerequisites +- +-The Installation Summary window is open. +- +- +-For an FCP-only installation, remove the DASD= option from the CMS configuration file or the rd.dasd= option from the parameter file to indicate that no DASD is present. +- +- +- +-Procedure +- +-From the Installation Summary window, click Installation Destination. The Installation Destination window opens, listing all available drives. +- +- +-Under the Specialized & Network Disks section, click Add a disk…. The storage devices selection window opens. +- +- +-Click Add ZFCP LUN. The Add zFCP Storage Target dialog box opens allowing you to add a FCP (Fibre Channel Protocol) storage device. +-IBM Z requires that you enter any FCP device manually so that the installation program can activate FCP LUNs. You can enter FCP devices either in the graphical installation, or as a unique parameter entry in the parameter or CMS configuration file. The values that you enter must be unique to each site that you configure. +- +- +-Type the 4 digit hexadecimal device number in the Device number field. +- +- +-Type the 16 digit hexadecimal World Wide Port Number (WWPN) in the WWPN field. +- +- +-Type the 16 digit hexadecimal FCP LUN identifier in the LUN field. +- +- +-Click Start Discovery to connect to the FCP device. +- +- +-The newly-added devices are displayed in the System z Devices tab of the Installation Destination window. +- +- +- +-Interactive creation of an FCP device is only possible in graphical mode. It is not possible to configure an FCP device interactively in text mode installation. +- +- +-Use only lower-case letters in hex values. If you enter an incorrect value and click Start Discovery, the installation program displays a warning. You can edit the configuration information and retry the discovery attempt. +- +- +-For more information about these values, consult the hardware documentation and check with your system administrator. +- +- +- +-
++ +
++ +
+ Installing to an NVDIMM device +-Non-Volatile Dual In-line Memory Module (NVDIMM) devices combine the performance of RAM with disk-like data persistence when no power is supplied. Under specific circumstances, Red Hat Enterprise Linux 8.3 Beta can boot and run from NVDIMM devices. ++Non-Volatile Dual In-line Memory Module (NVDIMM) devices combine the performance of RAM with disk-like data persistence when no power is supplied. Under specific circumstances, AlmaLinux 8.3 can boot and run from NVDIMM devices. +
+ Criteria for using an NVDIMM device as an installation target +-You can install Red Hat Enterprise Linux 8 to Non-Volatile Dual In-line Memory Module (NVDIMM) devices in sector mode on the Intel 64 and AMD64 architectures, supported by the nd_pmem driver. ++You can install AlmaLinux 8 to Non-Volatile Dual In-line Memory Module (NVDIMM) devices in sector mode on the Intel 64 and AMD64 architectures, supported by the nd_pmem driver. + + Conditions for using an NVDIMM device as storage + To use an NVDIMM device as storage, the following conditions must be satisfied: +@@ -1513,7 +1057,7 @@ +
+
+ Configuring an NVDIMM device using the graphical installation mode +-A Non-Volatile Dual In-line Memory Module (NVDIMM) device must be properly configured for use by Red Hat Enterprise Linux 8.3 Beta using the graphical installation. ++A Non-Volatile Dual In-line Memory Module (NVDIMM) device must be properly configured for use by AlmaLinux 8.3 using the graphical installation. + + Reconfiguration of a NVDIMM device process destroys any data stored on the device. + +@@ -1568,14 +1112,11 @@ + + + Configuring manual partitioning +-You can use manual partitioning to configure your disk partitions and mount points and define the file system that Red Hat Enterprise Linux is installed on. ++You can use manual partitioning to configure your disk partitions and mount points and define the file system that AlmaLinux is installed on. + +-Before installation, you should consider whether you want to use partitioned or unpartitioned disk devices. For more information, see the Knowledgebase article at https://access.redhat.com/solutions/163853. +- +-An installation of Red Hat Enterprise Linux requires a minimum of one partition but Red Hat recommends using at least the following partitions or volumes: PReP, /, /home, /boot, and swap. You can also create additional partitions and volumes as you require. +- +-An installation of Red Hat Enterprise Linux on IBM Power Systems servers requires a PReP boot partition. ++Before installation, you should consider whether you want to use partitioned or unpartitioned disk devices. + ++An installation of AlmaLinux requires a minimum of one partition but AlmaLinux recommends using at least the following partitions or volumes: PReP, /, /home, /boot, and swap. You can also create additional partitions and volumes as you require. + + To prevent data loss it is recommended that you back up your data before proceeding. If you are upgrading or creating a dual-boot system, you should back up any data you want to keep on your storage devices. + +@@ -1638,7 +1179,7 @@ + The dialog has a check box that you can use to remove all other partitions used by the system to which the deleted partition belongs. + + +-If there are no existing partitions and you want to create the recommended set of partitions as a starting point, select your preferred partitioning scheme from the left pane (default for Red Hat Enterprise Linux is LVM) and click the Click here to create them automatically link. ++If there are no existing partitions and you want to create the recommended set of partitions as a starting point, select your preferred partitioning scheme from the left pane (default for AlmaLinux is LVM) and click the Click here to create them automatically link. + A /boot partition, a / (root) volume, and a swap volume proportionate to the size of the available storage are created and listed in the left pane. These are the recommended file systems for a typical installation, but you can add additional file systems and mount points. + + +@@ -1689,14 +1230,11 @@ +
+
+ Configuring a mount point file system +-This procedure describes how to set the partitioning scheme for each mount point that was created manually. The available options are Standard Partition, LVM, and LVM Thin Provisioning. ++This procedure describes how to set the partitioning scheme for each mount point that was created manually. The available options are Standard Partition, LVM, and LVM Thin Provisioning. + + + +-Btfrs support has been removed in Red Hat Enterprise Linux 8.3 Beta. +- +- +-The /boot partition is always located on a standard partition, regardless of the value selected. ++The /boot partition is always located on a standard partition, regardless of the value selected. + + + +@@ -1804,23 +1342,23 @@ +
+
+ Preserving the /home directory +-In a RHEL 8 graphical installation, you can preserve the /home directory that was used on your RHEL 7 system. ++In a AlmaLinux 8 graphical installation, you can preserve the /home directory that was used on your RHEL-like 7 system. + +-Preserving /home is only possible if the /home directory is located on a separate /home partition on your RHEL 7 system. ++Preserving /home is only possible if the /home directory is located on a separate /home partition on your RHEL-like 7 system. + +-Preserving the /home directory that includes various configuration settings, makes it possible that the GNOME Shell environment on the new RHEL 8 system is set in the same way as it was on your RHEL 7 system. +-Note that this applies only for users on RHEL 8 with the same user name and ID as on the previous RHEL 7 system. +-Complete this procedure to preserve the /home directory from your RHEL 7 system. ++Preserving the /home directory that includes various configuration settings, makes it possible that the GNOME Shell environment on the new AlmaLinux 8 system is set in the same way as it was on your RHEL-like 7 system. ++Note that this applies only for users on AlmaLinux 8 with the same user name and ID as on the previous RHEL-like 7 system. ++Complete this procedure to preserve the /home directory from your RHEL-like 7 system. + + Prerequisites + +-RHEL 7 system is installed on your computer. ++RHEL-like 7 system is installed on your computer. + + +-The /home directory is located on a separate /home partition on your RHEL 7 system. ++The /home directory is located on a separate /home partition on your RHEL-like 7 system. + + +-The RHEL 8 Installation Summary window is currently displayed. ++The AlmaLinux 8 Installation Summary window is currently displayed. + + + +@@ -1847,7 +1385,7 @@ + + + +-Optional: You can also customize various aspects of the /home partition required for your RHEL 8 system as described in . However, to preserve /home from your RHEL 7 system, it is necessary to clear the Reformat check box. ++Optional: You can also customize various aspects of the /home partition required for your AlmaLinux 8 system as described in . However, to preserve /home from your RHEL-like 7 system, it is necessary to clear the Reformat check box. + + + After you customized all partitions according to your requirements, click Done. The Summary of changes dialog box opens. +@@ -1864,9 +1402,6 @@ + Creating software RAID + Follow the steps in this procedure to create a Redundant Arrays of Independent Disks (RAID) device. RAID devices are constructed from multiple storage devices that are arranged to provide increased performance and, in some configurations, greater fault tolerance. + A RAID device is created in one step and disks are added or removed as necessary. You can configure one RAID partition for each physical disk in your system, so the number of disks available to the installation program determines the levels of RAID device available. For example, if your system has two hard drives, you cannot create a RAID 10 device, as it requires a minimum of three separate disks. +- +-On IBM Z, the storage subsystem uses RAID transparently. You do not have to configure software RAID manually. +- + + Prerequisites + +@@ -1925,16 +1460,10 @@ + + Click the Device Type drop-down menu and select LVM. The Volume Group drop-down menu is displayed with the newly-created volume group name. + +-You cannot specify the size of the volume group’s physical extents in the configuration dialog. The size is always set to the default value of 4 MiB. If you want to create a volume group with different physical extents, you must create it manually by switching to an interactive shell and using the vgcreate command, or use a Kickstart file with the volgroup --pesize=size command. See the Performing an advanced RHEL installation document for more information about Kickstart. ++ You cannot specify the size of the volume group’s physical extents in the configuration dialog. The size is always set to the default value of 4 MiB. If you want to create a volume group with different physical extents, you must create it manually by switching to an interactive shell and using the vgcreate command, or use a Kickstart file with the volgroup --pesize=size command. + + + +- +-Additional resources +- +-For more information about LVM, see the Configuring and managing logical volumes document. +- +- +
+
+ Configuring an LVM logical volume +@@ -1954,7 +1483,7 @@ + Click Modify to configure the newly-created volume group. + The Configure Volume Group dialog box opens. + +-You cannot specify the size of the volume group’s physical extents in the configuration dialog. The size is always set to the default value of 4 MiB. If you want to create a volume group with different physical extents, you must create it manually by switching to an interactive shell and using the vgcreate command, or use a Kickstart file with the volgroup --pesize=size command. See the Performing an advanced RHEL installation document for more information about Kickstart. ++ You cannot specify the size of the volume group’s physical extents in the configuration dialog. The size is always set to the default value of 4 MiB. If you want to create a volume group with different physical extents, you must create it manually by switching to an interactive shell and using the vgcreate command, or use a Kickstart file with the volgroup --pesize=size command. + + + +@@ -2086,7 +1615,7 @@ + Click Save Changes to apply the changes and return to the Configuration window. + + +-When the installation process is complete, click Reboot to reboot and log in to your Red Hat Enterprise Linux 8.3 Beta system. ++When the installation process is complete, click Reboot to reboot and log in to your AlmaLinux 8.3 system. + + + +@@ -2129,13 +1658,13 @@ + +
+ +- ++ + Completing the installation + + Wait for the installation to complete. It might take a few minutes. + After the installation is complete, remove any installation media if it is not ejected automatically upon reboot. +-Red Hat Enterprise Linux 8 starts after your system’s normal power-up sequence is complete. If your system was installed on a workstation with the X Window System, applications to configure your system are launched. These applications guide you through initial configuration and you can set your system time and date, register your system with Red Hat, and more. If the X Window System is not installed, a login: prompt is displayed. +-To learn how to complete initial setup, register, and secure your system, see the Completing post-installation tasks section of the Performing a standard RHEL installation document. ++AlmaLinux 8 starts after your system’s normal power-up sequence is complete. If your system was installed on a workstation with the X Window System, applications to configure your system are launched. These applications guide you through initial configuration and you can set your system time and date and more. If the X Window System is not installed, a login: prompt is displayed. ++ + + +- +\ No newline at end of file ++ + +diff -Naur anaconda-user-help-8.3.3/rhel/en-US/rhel_help_placeholder.txt anaconda-user-help-8.3.3.alma/rhel/en-US/rhel_help_placeholder.txt +--- anaconda-user-help-8.3.3/rhel/en-US/rhel_help_placeholder.txt 2020-09-04 04:23:41.000000000 +0300 ++++ anaconda-user-help-8.3.3.alma/rhel/en-US/rhel_help_placeholder.txt 2021-01-22 09:39:53.962571589 +0300 +@@ -1 +1 @@ +-Help content for this screen is not yet available. See the installation instructions available online at https://access.redhat.com. ++Help content for this screen is not yet available. See the installation instructions available online at https://almalinux.org. +diff -Naur anaconda-user-help-8.3.3/rhel/en-US/rhel_help_placeholder.xml anaconda-user-help-8.3.3.alma/rhel/en-US/rhel_help_placeholder.xml +--- anaconda-user-help-8.3.3/rhel/en-US/rhel_help_placeholder.xml 2020-09-04 04:23:41.000000000 +0300 ++++ anaconda-user-help-8.3.3.alma/rhel/en-US/rhel_help_placeholder.xml 2021-01-22 09:40:23.715033095 +0300 +@@ -1 +1 @@ +-
Help content for this screen is not yet available. See the installation instructions available online at https://access.redhat.com/.
++
Help content for this screen is not yet available. See the installation instructions available online at https://almalinux.org/.
diff --git a/SPECS/anaconda-user-help.spec b/SPECS/anaconda-user-help.spec index d60a717..0e08594 100644 --- a/SPECS/anaconda-user-help.spec +++ b/SPECS/anaconda-user-help.spec @@ -2,7 +2,7 @@ Summary: Content for the Anaconda built-in help system Name: anaconda-user-help URL: https://pagure.io/install-guide Version: 26.1 -Release: 15%{?dist} +Release: 15%{?dist}.alma BuildArch: noarch # The tarball is created from the Fedora Installation Guide @@ -15,6 +15,8 @@ BuildArch: noarch Source0: %{name}-%{version}.tar.gz Source1: %{name}-blivet-gui.tar.gz +Patch0: anaconda-user-help-almalinux-branding.patch + License: CC-BY-SA BuildRequires: python3-devel BuildRequires: python3-lxml @@ -27,6 +29,7 @@ This package provides content for the Anaconda built-in help system. %prep %setup -q -a 1 +%patch0 -p1 %build %{__python3} prepare_anaconda_help_content.py @@ -40,6 +43,9 @@ cp -r blivetgui_help_content/* %{buildroot}%{_datadir}/anaconda/help %{_datadir}/anaconda/help/* %changelog +* Tue Jan 18 2022 Eduard Abdullin - 26.1-15.alma +- Debrand for AlmaLinux + * Mon Aug 09 2021 Mohan Boddu - 26.1-15 - Rebuilt for IMA sigs, glibc 2.34, aarch64 flags Related: rhbz#1991688