AlmaLinux changes

2021-09-02 10:35:19 +00:00 · 2021-09-02 10:35:19 +00:00 · e06e7c65f7
commit e06e7c65f7
parent 40ee8462de
2 changed files with 986 additions and 1 deletions
--- a/SOURCES/anaconda-user-help-almalinux-branding.patch
+++ 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 @@
 <info>
 <title>Customizing your installation</title>
 <date>2020-09-04</date>
 -<orgname>Red&#160;Hat</orgname>
 +<orgname>AlmaLinux</orgname>
 </info>
 <preface>
 <title/>
 -<simpara>When installing Red&#160;Hat Enterprise&#160;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 &amp; 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&#160;Hat Enterprise&#160;Linux installation using the Graphical User Interface (GUI). The GUI is the preferred method of installing Red&#160;Hat Enterprise&#160;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</title>
 <simpara>The installation program uses the language that you selected during installation.</simpara>
 <orderedlist numeration="arabic">
@@ -76,18 +76,18 @@
 <orderedlist numeration="arabic">
 <title>Procedure</title>
 <listitem>
 -<simpara>From the left-hand pane of the <emphasis role="strong">Welcome to Red Hat Enterprise Linux</emphasis> window, select a language. Alternatively, type your preferred language into the <emphasis role="strong">Search</emphasis> field.</simpara>
 +<simpara>From the left-hand pane of the <emphasis role="strong">Welcome to AlmaLinux</emphasis> window, select a language. Alternatively, type your preferred language into the <emphasis role="strong">Search</emphasis> field.</simpara>
 <note>
 <simpara>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 <emphasis role="strong">GeoIP</emphasis> module. If you used the <literal role="option">inst.lang=</literal> option on the boot command line or in your PXE server configuration, then the language that you define with the boot option is selected.</simpara>
 </note>
 </listitem>
 <listitem>
 -<simpara>From the right-hand pane of the <emphasis role="strong">Welcome to Red Hat Enterprise Linux</emphasis> window, select a location specific to your region.</simpara>
 +<simpara>From the right-hand pane of the <emphasis role="strong">Welcome to AlmaLinux</emphasis> window, select a location specific to your region.</simpara>
 </listitem>
 <listitem>
 <simpara>Click <guibutton>Continue</guibutton> to proceed to the <xref linkend="graphical-installation_graphical-installation"/> window.</simpara>
 <important>
 -<simpara>If you are installing a pre-release version of Red&#160;Hat Enterprise&#160;Linux, a warning message is displayed about the pre-release status of the installation media. Click <guibutton>I want to proceed</guibutton> to continue with the installation, or <guibutton>I want to exit</guibutton> to quit the installation and reboot the system.</simpara>
 +<simpara>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 <guibutton>I want to proceed</guibutton> to continue with the installation, or <guibutton>I want to exit</guibutton> to quit the installation and reboot the system.</simpara>
 </important>
 </listitem>
 </orderedlist>
@@ -105,13 +105,13 @@
 <section xml:id="_configuring_keyboard_language_and_time_and_date_settings">
 <title>Configuring keyboard, language, and time and date settings</title>
 <note>
 -<simpara>Keyboard, Language, and Time and Date Settings are configured by default as part of <xref linkend="installing-rhel-using-anaconda_graphical-installation"/>.
 +<simpara>Keyboard, Language, and Time and Date Settings are configured by default as part of <xref linkend="installing-alma-using-anaconda_graphical-installation"/>.
 To change any of the settings, complete the following steps, otherwise proceed to <xref linkend="configuring-software-settings_graphical-installation"/>.</simpara>
 </note>
 <orderedlist numeration="arabic">
 <title>Procedure: Configuring keyboard settings</title>
 <listitem>
 -<simpara>From the <emphasis role="strong">Installation Summary</emphasis> window, click <emphasis role="strong">Keyboard</emphasis>. The default layout depends on the option selected in <xref linkend="installing-rhel-using-anaconda_graphical-installation"/>.</simpara>
 +<simpara>From the <emphasis role="strong">Installation Summary</emphasis> window, click <emphasis role="strong">Keyboard</emphasis>. The default layout depends on the option selected in <xref linkend="installing-alma-using-anaconda_graphical-installation"/>.</simpara>
 <orderedlist numeration="loweralpha">
 <listitem>
 <simpara>Click <guibutton>+</guibutton> to open the <emphasis role="strong">Add a Keyboard Layout</emphasis> window and change to a different layout.</simpara>
@@ -156,8 +156,8 @@
 <listitem>
 <simpara>From the <emphasis role="strong">Installation Summary</emphasis> window, click <emphasis role="strong">Time &amp; Date</emphasis>. The <emphasis role="strong">Time &amp; Date</emphasis> window opens.</simpara>
 <note>
 -<simpara>The <emphasis role="strong">Time &amp; Date</emphasis> settings are configured by default based on the settings you selected in <xref linkend="installing-rhel-using-anaconda_graphical-installation"/>.</simpara>
 -<simpara>The list of cities and regions come from the Time Zone Database (<literal role="package">tzdata</literal>) public domain that is maintained by the Internet Assigned Numbers Authority (IANA). Red&#160;Hat can not add cities or regions to this database. You can find more information at the <link xl:href="http://www.iana.org/time-zones">IANA official website</link>.</simpara>
 +<simpara>The <emphasis role="strong">Time &amp; Date</emphasis> settings are configured by default based on the settings you selected in <xref linkend="installing-alma-using-anaconda_graphical-installation"/>.</simpara>
 +<simpara>The list of cities and regions come from the Time Zone Database (<literal role="package">tzdata</literal>) 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 <link xl:href="http://www.iana.org/time-zones">IANA official website</link>.</simpara>
 </note>
 <orderedlist numeration="loweralpha">
 <listitem>
@@ -191,9 +191,9 @@
 <simpara>This section contains information about configuring Installation Destination, KDUMP, Network and Host Name, and Security Policy.</simpara>
 <section xml:id="configuring-system-settings_configuring-system-settings">
 <title>Configuring installation destination</title>
 -<simpara>Use the <emphasis role="strong">Installation Destination</emphasis> window to configure the storage options, for example, the disks that you want to use as the installation target for your Red&#160;Hat Enterprise&#160;Linux installation. You must select at least one disk.</simpara>
 +<simpara>Use the <emphasis role="strong">Installation Destination</emphasis> 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.</simpara>
 <warning>
 -<simpara>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&#160;Hat Enterprise&#160;Linux as a second system, or if you are upgrading a previous release of Red&#160;Hat Enterprise&#160;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.</simpara>
 +<simpara>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.</simpara>
 </warning>
 <important>
 <itemizedlist>
@@ -203,10 +203,10 @@
 If you choose to partition your system automatically, you should manually edit your <literal>/boot</literal> partition.</simpara>
 </listitem>
 <listitem>
 -<simpara>To configure the Red&#160;Hat Enterprise&#160;Linux boot loader to <emphasis>chain load</emphasis> from a different boot loader, you must specify the boot drive manually by clicking the <emphasis role="strong">Full disk summary and bootloader</emphasis> link from the <emphasis role="strong">Installation Destination</emphasis> window.</simpara>
 +<simpara>To configure the AlmaLinux boot loader to <emphasis>chain load</emphasis> from a different boot loader, you must specify the boot drive manually by clicking the <emphasis role="strong">Full disk summary and bootloader</emphasis> link from the <emphasis role="strong">Installation Destination</emphasis> window.</simpara>
 </listitem>
 <listitem>
 -<simpara>When you install Red&#160;Hat Enterprise&#160;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 <emphasis role="strong">Installation Destination</emphasis> window. Alternatively, proceed to manual partitioning.</simpara>
 +<simpara>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 <emphasis role="strong">Installation Destination</emphasis> window. Alternatively, proceed to manual partitioning.</simpara>
 </listitem>
 </itemizedlist>
 </important>
@@ -222,7 +222,7 @@
 <listitem>
 <simpara>From the <emphasis role="strong">Local Standard Disks</emphasis> 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.</simpara>
 <note>
 -<simpara>All locally available storage devices (SATA, IDE and SCSI hard drives, USB flash and external disks) are displayed under <emphasis role="strong">Local Standard Disks</emphasis>. Any storage devices connected after the installation program has started are not detected. If you use a removable drive to install Red&#160;Hat Enterprise&#160;Linux, your system is unusable if you remove the device.</simpara>
 +<simpara>All locally available storage devices (SATA, IDE and SCSI hard drives, USB flash and external disks) are displayed under <emphasis role="strong">Local Standard Disks</emphasis>. 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.</simpara>
 </note>
 </listitem>
 <listitem>
@@ -252,7 +252,7 @@
 </important>
 </listitem>
 <listitem>
 -<simpara>Optional: To reclaim space from an existing partitioning layout, select the <emphasis role="strong">I would like to make additional space available</emphasis> check box. For example, if a disk you want to use already contains a different operating system and you want to make this system&#8217;s partitions smaller to allow more room for Red&#160;Hat Enterprise&#160;Linux.</simpara>
 +<simpara>Optional: To reclaim space from an existing partitioning layout, select the <emphasis role="strong">I would like to make additional space available</emphasis> check box. For example, if a disk you want to use already contains a different operating system and you want to make this system&#8217;s partitions smaller to allow more room for AlmaLinux.</simpara>
 </listitem>
 <listitem>
 <simpara>Optional: Select <emphasis role="strong">Encrypt my data</emphasis> to encrypt all partitions except the ones needed to boot the system (such as <literal>/boot</literal>) using <emphasis>Linux Unified Key Setup</emphasis> (LUKS). Encrypting your hard drive is recommended.</simpara>
@@ -266,7 +266,7 @@
 <listitem>
 <simpara>Click <guibutton>Save Passphrase</guibutton> to complete disk encryption.</simpara>
 <warning>
 -<simpara>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 <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/performing_an_advanced_rhel_installation/index/"><emphasis>Performing an advanced RHEL installation</emphasis></link> document for information.</simpara>
 +	<simpara>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.</simpara>
 </warning>
 </listitem>
 </orderedlist>
@@ -283,7 +283,7 @@
 <simpara>Click <guibutton>Done</guibutton>.</simpara>
 <orderedlist numeration="loweralpha">
 <listitem>
 -<simpara>If you selected <emphasis role="strong">automatic partitioning</emphasis> and <emphasis role="strong">I would like to make additional space available</emphasis>, or if there is not enough free space on your selected hard drives to install Red&#160;Hat Enterprise&#160;Linux, the <emphasis role="strong">Reclaim Disk Space</emphasis> dialog box opens when you click <guibutton>Done</guibutton>, 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.</simpara>
 +<simpara>If you selected <emphasis role="strong">automatic partitioning</emphasis> and <emphasis role="strong">I would like to make additional space available</emphasis>, or if there is not enough free space on your selected hard drives to install AlmaLinux, the <emphasis role="strong">Reclaim Disk Space</emphasis> dialog box opens when you click <guibutton>Done</guibutton>, 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.</simpara>
 <warning>
 <simpara>If you <emphasis role="strong">delete</emphasis> a partition, all data on that partition is lost. If you want to preserve your data, use the <emphasis role="strong">Shrink</emphasis> option, not the <emphasis role="strong">Delete</emphasis> option.</simpara>
 </warning>
@@ -294,7 +294,7 @@
 <listitem>
 <simpara>To reclaim space, select a disk or partition, and click either the <guibutton>Delete</guibutton> button to delete that partition, or all partitions on a selected disk, or click <guibutton>Shrink</guibutton> to use free space on a partition while preserving the existing data.</simpara>
 <note>
 -<simpara>Alternatively, you can click <guibutton>Delete all</guibutton>, this deletes all existing partitions on all disks and makes this space available to Red&#160;Hat Enterprise&#160;Linux. Existing data on all disks is lost.</simpara>
 +<simpara>Alternatively, you can click <guibutton>Delete all</guibutton>, this deletes all existing partitions on all disks and makes this space available to AlmaLinux. Existing data on all disks is lost.</simpara>
 </note>
 </listitem>
 <listitem>
@@ -308,13 +308,13 @@
 </important>
 <section xml:id="boot-loader-installation_configuring-system-settings">
 <title>Configuring boot loader</title>
 -<simpara>Red&#160;Hat Enterprise&#160;Linux uses GRand Unified Bootloader version 2 (<emphasis role="strong"><phrase role="application">GRUB2</phrase></emphasis>) as the boot loader for AMD64 and Intel 64, IBM Power Systems, and ARM. For IBM&#160;Z, the <emphasis role="strong">zipl</emphasis> boot loader is used.</simpara>
 +<simpara>AlmaLinux uses GRand Unified Bootloader version 2 (<emphasis role="strong"><phrase role="application">GRUB2</phrase></emphasis>) as the boot loader for AMD64, Intel 64, and ARM.</simpara>
 <simpara>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. <emphasis role="strong"><phrase role="application">GRUB2</phrase></emphasis> 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.</simpara>
 <warning>
 <simpara>Installing <emphasis role="strong"><phrase role="application">GRUB2</phrase></emphasis> may overwrite your existing boot loader.</simpara>
 </warning>
 -<simpara>If an operating system is already installed, the Red&#160;Hat Enterprise&#160;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.</simpara>
 -<simpara>If you are installing a Red&#160;Hat Enterprise&#160;Linux system with more than one disk, you might want to manually specify the disk where you want to install the boot loader.</simpara>
 +<simpara>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.</simpara>
 +<simpara>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.</simpara>
 <orderedlist numeration="arabic">
 <title>Procedure</title>
 <listitem>
@@ -358,7 +358,7 @@
 </listitem>
 </orderedlist>
 <note>
 -<simpara>The amount of memory that you reserve is determined by your system architecture (AMD64 and Intel&#160;64 have different requirements than IBM Power) as well as the total amount of system memory. In most cases, automatic reservation is satisfactory.</simpara>
 +<simpara>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.</simpara>
 </note>
 <important>
 <simpara>Additional settings, such as the location where kernel crash dumps will be saved, can only be configured after the installation using either the <emphasis role="strong"><phrase role="application">system-config-kdump</phrase></emphasis> graphical interface, or manually in the <literal>/etc/kdump.conf</literal> configuration file.</simpara>
@@ -398,7 +398,7 @@
 <note>
 <itemizedlist>
 <listitem>
 -<simpara>There are several types of network device naming standards used to identify network devices with persistent names, for example, <literal>em1</literal> and <literal>wl3sp0</literal>. For information about these standards, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_and_managing_networking/index/"><emphasis>Configuring and managing networking</emphasis></link> document.</simpara>
 +	<simpara>There are several types of network device naming standards used to identify network devices with persistent names, for example, <literal>em1</literal> and <literal>wl3sp0</literal>.</simpara>
 </listitem>
 <listitem>
 <simpara>The host name can be either a fully-qualified domain name (FQDN) in the format <emphasis>hostname.domainname</emphasis>, 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 <literal>localhost.localdomain</literal> 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 <literal>NetworkManager</literal> using DHCP or DNS.</simpara>
@@ -453,7 +453,6 @@
 <title>Editing network interface configuration</title>
 <simpara>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.</simpara>
 <note>
 -<simpara>On IBM&#160;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.</simpara>
 </note>
 <orderedlist numeration="arabic">
 <title>Procedure</title>
@@ -479,7 +478,7 @@
 <important>
 <itemizedlist>
 <listitem>
 -<simpara>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 <literal>nm-connection-editor</literal> tool, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_and_managing_networking/index?lb_target=production"><emphasis>Configuring and managing networking</emphasis></link> document.</simpara>
 +<simpara>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.</simpara>
 </listitem>
 <listitem>
 <simpara>You can enable or disable all users on the system from connecting to this network using the <emphasis role="strong">All users may connect to this network</emphasis> option. If you disable this option, only <literal role="systemitem">root</literal> will be able to connect to this network.</simpara>
@@ -551,21 +550,13 @@
 </listitem>
 </orderedlist>
 </section>
 -<section xml:id="additional-resources_network-hostname">
 -<title>Additional resources</title>
 -<itemizedlist>
 -<listitem>
 -<simpara>To learn more about network configuration after installation, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_and_managing_networking/index/"><emphasis>Configuring and managing networking</emphasis></link> document.</simpara>
 -</listitem>
 -</itemizedlist>
 -</section>
 </section>
 <section xml:id="security-policy_configuring-system-settings">
 <title>Configuring Security Policy</title>
 -<simpara>This section contains information about the Red&#160;Hat Enterprise&#160;Linux 8.3 Beta security policy and how to configure it for use on your system.</simpara>
 +<simpara>This section contains information about the AlmaLinux 8.3 security policy and how to configure it for use on your system.</simpara>
 <section xml:id="about-security-policy_security-policy">
 <title>About security policy</title>
 -<simpara>The Red&#160;Hat Enterprise&#160;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.</simpara>
 +<simpara>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.</simpara>
 <simpara>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 <emphasis role="strong"><phrase role="package">openscap-scanner</phrase></emphasis> 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 <literal>/root/openscap_data</literal> directory on the installed system. You can also load additional profiles from an HTTP, HTTPS, or FTP server.</simpara>
 </section>
 <section xml:id="configuring-security-policy_security-policy">
@@ -619,366 +610,18 @@
 <listitem>
 <simpara><literal role="literal">scap-security-guide(8)</literal> - The manual page for the <literal role="literal">scap-security-guide</literal> project contains information about SCAP security profiles, including examples on how to utilize the provided benchmarks using the OpenSCAP utility.</simpara>
 </listitem>
 -<listitem>
 -<simpara>Red&#160;Hat Enterprise&#160;Linux security compliance information is available in the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/security_hardening/index/"><emphasis>Security hardening</emphasis></link> document.</simpara>
 -</listitem>
 </itemizedlist>
 </section>
 </section>
 </chapter>
 <chapter xml:id="configuring-software-settings_graphical-installation">
 <title>Configuring software options</title>
 -<simpara>This section contains information about configuring Red Hat Content Delivery Network (CDN), your installation source and software selection settings, and activating a repository.</simpara>
 -<section xml:id="connect-to-red-hat_configuring-software-settings">
 -<title>Configuring Connect to Red Hat</title>
 -<simpara>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.</simpara>
 -<simpara>Registering and installing RHEL from the CDN provides the following benefits:</simpara>
 -<itemizedlist>
 -<listitem>
 -<simpara>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.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>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.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Integrated support for connecting to Red Hat Insights and enabling System Purpose.</simpara>
 -</listitem>
 -</itemizedlist>
 -<section xml:id="system_purposes-adoc_connect-to-red-hat">
 -<title>Introduction to System Purpose</title>
 -<simpara>System Purpose is an optional but recommended feature of the Red&#160;Hat Enterprise&#160;Linux installation. You use System Purpose to record the intended use of a Red&#160;Hat Enterprise&#160;Linux 8 system, and ensure that the entitlement server auto-attaches the most appropriate subscription to your system.</simpara>
 -<simpara>Benefits include:</simpara>
 -<itemizedlist>
 -<listitem>
 -<simpara>In-depth system-level information for system administrators and business operations.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Reduced overhead when determining why a system was procured and its intended purpose.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Improved customer experience of Subscription Manager auto-attach as well as automated discovery and reconciliation of system usage.</simpara>
 -</listitem>
 -</itemizedlist>
 -<simpara>You can enter System Purpose data in one of the following ways:</simpara>
 -<itemizedlist>
 -<listitem>
 -<simpara>During image creation</simpara>
 -</listitem>
 -<listitem>
 -<simpara>During a GUI installation when using <emphasis role="strong">Connect to Red Hat</emphasis> to register your system and attach your Red Hat subscription</simpara>
 -</listitem>
 -<listitem>
 -<simpara>During a Kickstart installation when using Kickstart automation scripts</simpara>
 -</listitem>
 -<listitem>
 -<simpara>After installation using the <emphasis role="strong">syspurpose</emphasis> command-line (CLI) tool</simpara>
 -</listitem>
 -</itemizedlist>
 -<simpara>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.</simpara>
 -<itemizedlist>
 -<listitem>
 -<simpara><emphasis role="strong">Role</emphasis></simpara>
 -<itemizedlist>
 -<listitem>
 -<simpara>Red Hat Enterprise Linux Server</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Red Hat Enterprise Linux Workstation</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Red Hat Enterprise Linux Compute Node</simpara>
 -</listitem>
 -</itemizedlist>
 -</listitem>
 -<listitem>
 -<simpara><emphasis role="strong">Service Level Agreement</emphasis></simpara>
 -<itemizedlist>
 -<listitem>
 -<simpara>Premium</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Standard</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Self-Support</simpara>
 -</listitem>
 -</itemizedlist>
 -</listitem>
 -<listitem>
 -<simpara><emphasis role="strong">Usage</emphasis></simpara>
 -<itemizedlist>
 -<listitem>
 -<simpara>Production</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Development/Test</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Disaster Recovery</simpara>
 -</listitem>
 -</itemizedlist>
 -</listitem>
 -</itemizedlist>
 -<itemizedlist>
 -<title>Additional resources</title>
 -<listitem>
 -<simpara>For more information about Image Builder, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/composing_a_customized_rhel_system_image/index/"><emphasis>Composing a customized RHEL system image</emphasis></link> document.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>For more information about Kickstart, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/performing_an_advanced_rhel_installation/index/"><emphasis>Performing an advanced RHEL installation</emphasis></link> document.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>For more information about Subscription Manager, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_subscription_management/1/html-single/rhsm/index/"><emphasis>Using and Configuring Red Hat Subscription Manager</emphasis></link> document.</simpara>
 -</listitem>
 -</itemizedlist>
 -</section>
 -<section xml:id="configuring-connect-to-redhat_connect-to-red-hat">
 -<title>Configuring Connect to Red Hat options</title>
 -<simpara>Use the following procedure to configure the Connect to Red Hat options in the GUI.</simpara>
 -<note>
 -<simpara>You can register to the CDN using either your Red Hat account or your activation key details.</simpara>
 -</note>
 -<orderedlist numeration="arabic">
 -<title>Procedure</title>
 -<listitem>
 -<simpara>Click <emphasis role="strong">Account</emphasis>.</simpara>
 -<orderedlist numeration="loweralpha">
 -<listitem>
 -<simpara>Enter your Red Hat Customer Portal username and password details.</simpara>
 -</listitem>
 -</orderedlist>
 -</listitem>
 -<listitem>
 -<simpara>Optional: Click <emphasis role="strong">Activation Key</emphasis>.</simpara>
 -<orderedlist numeration="loweralpha">
 -<listitem>
 -<simpara>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.</simpara>
 -</listitem>
 -</orderedlist>
 -</listitem>
 -<listitem>
 -<simpara>Select the <emphasis role="strong">Set System Purpose</emphasis> 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.</simpara>
 -<orderedlist numeration="loweralpha">
 -<listitem>
 -<simpara>Select the required <emphasis role="strong">Role</emphasis>, <emphasis role="strong">SLA</emphasis>, and <emphasis role="strong">Usage</emphasis> from the corresponding drop-down lists.</simpara>
 -</listitem>
 -</orderedlist>
 -</listitem>
 -<listitem>
 -<simpara>The <emphasis role="strong">Connect to Red Hat Insights</emphasis> check box is enabled by default. Clear the check box if you do not want to connect to Red Hat Insights.</simpara>
 -<note>
 -<simpara>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.</simpara>
 -</note>
 -</listitem>
 -<listitem>
 -<simpara>Optional: Expand <emphasis role="strong">Options</emphasis>.</simpara>
 -<orderedlist numeration="loweralpha">
 -<listitem>
 -<simpara>Select the <emphasis role="strong">Use HTTP proxy</emphasis> check box if your network environment only allows external Internet access or access to content servers through an HTTP proxy. Clear the <emphasis role="strong">Use HTTP proxy</emphasis> check box if an HTTP proxy is not used.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>If you are running Satellite Server or performing internal testing, select the <emphasis role="strong">Custom server URL</emphasis> and  <emphasis role="strong">Custom base URL</emphasis> check boxes and enter the required details.</simpara>
 -<important>
 -<itemizedlist>
 -<listitem>
 -<simpara>The <emphasis role="strong">Custom server URL</emphasis> field does not require the HTTP protocol, for example <literal>nameofhost.com</literal>. However, the <emphasis role="strong">Custom base URL</emphasis> field requires the HTTP protocol.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>To change the <emphasis role="strong">Custom base URL</emphasis> after registration, you must unregister, provide the new details, and then re-register.</simpara>
 -</listitem>
 -</itemizedlist>
 -</important>
 -</listitem>
 -</orderedlist>
 -</listitem>
 -<listitem>
 -<simpara>Click <guibutton>Register</guibutton> to register the system. When the system is successfully registered and subscriptions are attached, the <emphasis role="strong">Connect to Red Hat</emphasis> window displays the attached subscription details.</simpara>
 -<note>
 -<simpara>Depending on the amount of subscriptions, the registration and attachment process might take up to a minute to complete.</simpara>
 -</note>
 -</listitem>
 -<listitem>
 -<simpara>Click <guibutton>Done</guibutton> to return to the <emphasis role="strong">Installation Summary</emphasis> window.</simpara>
 -<orderedlist numeration="loweralpha">
 -<listitem>
 -<simpara>A <emphasis>Registered</emphasis> message is displayed under <emphasis role="strong">Connect to Red Hat</emphasis>.</simpara>
 -</listitem>
 -</orderedlist>
 -</listitem>
 -</orderedlist>
 -</section>
 -<section xml:id="how-the-default-installation-repo-works-in-cdn_connect-to-red-hat">
 -<title>Installation source repository after system registration</title>
 -<simpara>The installation source repository used after system registration is dependent on how the system was booted.</simpara>
 -<variablelist>
 -<varlistentry>
 -<term>System booted from the Boot ISO or the Binary DVD ISO image file</term>
 -<listitem>
 -<simpara>If you booted the RHEL installation using either the <literal>Boot ISO</literal> or the <literal>Binary DVD ISO</literal> image file with the default boot parameters, the installation program automatically switches the installation source repository to the CDN after registration.</simpara>
 -</listitem>
 -</varlistentry>
 -<varlistentry>
 -<term>System booted with the <literal>inst.repo=&lt;URL&gt;</literal> boot parameter</term>
 -<listitem>
 -<simpara>If you booted the RHEL installation with the <literal>inst.repo=&lt;URL&gt;</literal> 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 <emphasis role="strong">Red Hat CDN</emphasis> option in the <emphasis role="strong">Installation Source</emphasis> 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.</simpara>
 -</listitem>
 -</varlistentry>
 -</variablelist>
 -<important>
 -<itemizedlist>
 -<listitem>
 -<simpara>You can switch the installation source repository to the CDN using the <literal>rhsm</literal> Kickstart command only if you do not specify an installation source using <literal>inst.repo=</literal> on the kernel command line or the <literal>url</literal> command in the Kickstart file. You must use <literal>inst.stage2=&lt;URL&gt;</literal> on the kernel command line to fetch the installation image, but not specify the installation source.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>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 <literal>rhsm</literal> 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.</simpara>
 -</listitem>
 -</itemizedlist>
 -</important>
 -</section>
 -<section xml:id="verifying-registration-from-cdn-using-gui_connect-to-red-hat">
 -<title>Verifying your system registration from the CDN</title>
 -<simpara>Use this procedure to verify that your system is registered to the CDN using the GUI.</simpara>
 -<warning>
 -<simpara>You can only verify your registration from the CDN if you have <emphasis role="strong">not</emphasis> clicked the <emphasis role="strong">Begin Installation</emphasis> button from the <emphasis role="strong">Installation Summary</emphasis> window. Once the <emphasis role="strong">Begin Installation</emphasis> button is clicked, you cannot return to the Installation Summary window to verify your registration.</simpara>
 -</warning>
 -<itemizedlist>
 -<title>Prerequisite</title>
 -<listitem>
 -<simpara>You have completed the registration process as documented in the <xref linkend="register-and-install-from-cdn-using-gui_register-and-install-from-cdn"/> and <emphasis>Registered</emphasis> is displayed under <emphasis role="strong">Connect to Red Hat</emphasis> on the <emphasis role="strong">Installation Summary</emphasis> window.</simpara>
 -</listitem>
 -</itemizedlist>
 -<orderedlist numeration="arabic">
 -<title>Procedure</title>
 -<listitem>
 -<simpara>From the <emphasis role="strong">Installation Summary</emphasis> window, select <emphasis role="strong">Connect to Red Hat</emphasis>.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>The window opens and displays a registration summary:</simpara>
 -<variablelist>
 -<varlistentry>
 -<term>Method</term>
 -<listitem>
 -<simpara>The registered account name or activation keys are displayed.</simpara>
 -</listitem>
 -</varlistentry>
 -<varlistentry>
 -<term>System Purpose</term>
 -<listitem>
 -<simpara>If set, the role, SLA, and usage details are displayed.</simpara>
 -</listitem>
 -</varlistentry>
 -<varlistentry>
 -<term>Insights</term>
 -<listitem>
 -<simpara>If enabled, the Insights details are displayed.</simpara>
 -</listitem>
 -</varlistentry>
 -<varlistentry>
 -<term>Number of subscriptions</term>
 -<listitem>
 -<simpara>The number of subscriptions attached are displayed.</simpara>
 -</listitem>
 -</varlistentry>
 -</variablelist>
 -</listitem>
 -<listitem>
 -<simpara>Verify that the registration summary matches the details that were entered.</simpara>
 -</listitem>
 -</orderedlist>
 -</section>
 -<section xml:id="unregistering-your-system-from-cdn-using-gui_connect-to-red-hat">
 -<title>Unregistering your system from the CDN</title>
 -<simpara>Use this procedure to unregister your system from the CDN using the GUI.</simpara>
 -<warning>
 -<itemizedlist>
 -<listitem>
 -<simpara>You can unregister from the CDN if you have <emphasis role="strong">not</emphasis> clicked the <guibutton>Begin Installation</guibutton> button from the <emphasis role="strong">Installation Summary</emphasis> window. Once the <guibutton>Begin Installation</guibutton> button is clicked, you cannot return to the Installation Summary window to unregister your registration.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>When unregistering, the installation program switches to the first available repository, in the following order:</simpara>
 -<orderedlist numeration="loweralpha">
 -<listitem>
 -<simpara>The URL used in the inst.repo=&lt;URL&gt; boot parameter on the kernel command line.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>An automatically detected repository on the installation media (USB or DVD).</simpara>
 -</listitem>
 -</orderedlist>
 -</listitem>
 -</itemizedlist>
 -</warning>
 -<itemizedlist>
 -<title>Prerequisite</title>
 -<listitem>
 -<simpara>You have completed the registration process as documented in the <xref linkend="register-and-install-from-cdn-using-gui_register-and-install-from-cdn"/> and <emphasis>Registered</emphasis> is displayed under <emphasis role="strong">Connect to Red Hat</emphasis> on the <emphasis role="strong">Installation Summary</emphasis> window.</simpara>
 -</listitem>
 -</itemizedlist>
 -<orderedlist numeration="arabic">
 -<title>Procedure</title>
 -<listitem>
 -<simpara>From the <emphasis role="strong">Installation Summary</emphasis> window, select <emphasis role="strong">Connect to Red Hat</emphasis>.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>The <emphasis role="strong">Connect to Red Hat</emphasis> window opens and displays a registration summary:</simpara>
 -<variablelist>
 -<varlistentry>
 -<term>Method</term>
 -<listitem>
 -<simpara>The registered account name or activation keys used are displayed.</simpara>
 -</listitem>
 -</varlistentry>
 -<varlistentry>
 -<term>System Purpose</term>
 -<listitem>
 -<simpara>If set, the role, SLA, and usage details are displayed.</simpara>
 -</listitem>
 -</varlistentry>
 -<varlistentry>
 -<term>Insights</term>
 -<listitem>
 -<simpara>If enabled, the Insights details are displayed.</simpara>
 -</listitem>
 -</varlistentry>
 -<varlistentry>
 -<term>Number of subscriptions</term>
 -<listitem>
 -<simpara>The number of subscriptions attached are displayed.</simpara>
 -</listitem>
 -</varlistentry>
 -</variablelist>
 -</listitem>
 -<listitem>
 -<simpara>Click <guibutton>Unregister</guibutton> to remove the registration from the CDN. The original registration details are displayed with a <emphasis role="strong">Not registered</emphasis> message displayed in the lower-middle part of the window.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Click <guibutton>Done</guibutton> to return to the <emphasis role="strong">Installation Summary</emphasis> window.</simpara>
 -</listitem>
 -<listitem>
 -<simpara><emphasis role="strong">Connect to Red Hat</emphasis> displays a <emphasis>Not registered</emphasis> message, and <emphasis role="strong">Software Selection</emphasis> displays a <emphasis>Red Hat CDN requires registration</emphasis> message.</simpara>
 -</listitem>
 -</orderedlist>
 -<note>
 -<simpara>After unregistering, it is possible to register your system again. Click <emphasis role="strong">Connect to Red Hat</emphasis>. The previously entered details are populated. Edit the original details, or update the fields based on the account, purpose, and connection. Click <guibutton>Register</guibutton> to complete.</simpara>
 -</note>
 -<itemizedlist xml:id="related-information-connect-to-red-hat">
 -<title>Related information</title>
 -<listitem>
 -<simpara>For information about Red Hat Insights, see the <link xl:href="https://access.redhat.com/documentation/or-in/red_hat_insights/1.0/"><emphasis>Red Hat Insights product documentation</emphasis></link>.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>For information about Activation Keys, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_subscription_management/1/html/using_red_hat_subscription_management/activation_keys_con"><emphasis>Understanding Activation Keys</emphasis></link> chapter of the <emphasis>Using Red Hat Subscription Management</emphasis> document.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>For information about how to set up an HTTP proxy for Subscription Manager, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_subscription_management/1/html-single/rhsm/index#repos-proxy"><emphasis>Using an HTTP proxy</emphasis></link> chapter of the <emphasis>Using and Configuring Red Hat Subscription Manager</emphasis> document.</simpara>
 -</listitem>
 -</itemizedlist>
 -</section>
 -</section>
 +<simpara>This section contains information about configuring your installation source and software selection settings, and activating a repository.</simpara>
 <section xml:id="configuring-installation-source_configuring-software-settings">
 <title>Configuring installation source</title>
 -<simpara>Complete the steps in this procedure to configure an installation source from either auto-detected installation media, Red Hat CDN, or the network.</simpara>
 +<simpara>Complete the steps in this procedure to configure an installation source from either auto-detected installation media or the network.</simpara>
 <note>
 -<simpara>When the <emphasis role="strong">Installation Summary</emphasis> 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&#160;Hat Enterprise&#160;Linux Server DVD configures the source as local media.</simpara>
 +<simpara>When the <emphasis role="strong">Installation Summary</emphasis> 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.</simpara>
 </note>
 <itemizedlist>
 <title>Prerequisites</title>
@@ -1011,7 +654,7 @@
 <simpara><emphasis role="strong">No additional configuration is necessary as the BaseOS and AppStream repositories are installed as part of the full installation image.</emphasis></simpara>
 </listitem>
 <listitem>
 -<simpara><emphasis role="strong">Do not disable the AppStream repository check box if you want a full Red&#160;Hat Enterprise&#160;Linux&#160;8 installation.</emphasis></simpara>
 +<simpara><emphasis role="strong">Do not disable the AppStream repository check box if you want a full AlmaLinux&#160;8 installation.</emphasis></simpara>
 </listitem>
 </itemizedlist>
 </important>
@@ -1019,9 +662,6 @@
 </orderedlist>
 </listitem>
 <listitem>
 -<simpara>Optional: Select the <emphasis role="strong">Red Hat CDN</emphasis> option to register your system, attach RHEL subscriptions, and install RHEL from the Red Hat Content Delivery Network (CDN). For more information, see the <emphasis>Registering and installing RHEL from the CDN</emphasis> section.</simpara>
 -</listitem>
 -<listitem>
 <simpara>Optional: Select the <emphasis role="strong">On the network</emphasis> option to download and install packages from a network location instead of local media.</simpara>
 <note>
 <itemizedlist>
@@ -1102,15 +742,14 @@
 </listitem>
 </itemizedlist>
 <simpara>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 <literal role="filename"><emphasis>repository</emphasis>/repodata/*-comps-<emphasis>repository</emphasis>.<emphasis>architecture</emphasis>.xml</literal> 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 <literal>&lt;environment&gt;</literal> tag, and additional software packages are marked by the <literal>&lt;group&gt;</literal> tag.</simpara>
 -<simpara>If you are unsure about which packages to install, Red Hat recommends that you select the <emphasis role="strong">Minimal Install</emphasis> base environment. Minimal install installs a basic version of Red&#160;Hat Enterprise&#160;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 <emphasis role="strong">Yum package manager</emphasis> to install additional software.
 -For more information about Yum package manager, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_basic_system_settings/index/"><emphasis>Configuring basic system settings</emphasis></link> document.</simpara>
 +<simpara>If you are unsure about which packages to install, AlmaLinux recommends that you select the <emphasis role="strong">Minimal Install</emphasis> 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 <emphasis role="strong">Yum package manager</emphasis> to install additional software.</simpara>
 <note>
 <itemizedlist>
 <listitem>
 -<simpara>The <literal>yum group list</literal> command lists all package groups from yum repositories. See the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_basic_system_settings/index/"><emphasis>Configuring basic system settings</emphasis></link> document for more information.</simpara>
 +<simpara>The <literal>yum group list</literal> command lists all package groups from yum repositories.</simpara>
 </listitem>
 <listitem>
 -<simpara>If you need to control which packages are installed, you can use a Kickstart file and define the packages in the <literal>%packages</literal> section. See the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/performing_an_advanced_rhel_installation/index/"><emphasis>Performing an advanced RHEL installation</emphasis></link> document for information about installing Red&#160;Hat Enterprise&#160;Linux using Kickstart.</simpara>
 +<simpara>If you need to control which packages are installed, you can use a Kickstart file and define the packages in the <literal>%packages</literal> section.</simpara>
 </listitem>
 </itemizedlist>
 </note>
@@ -1146,13 +785,10 @@
 </orderedlist>
 </section>
 </chapter>
 +
 <chapter xml:id="storage-devices_graphical-installation">
 <title>Configuring storage devices</title>
 -<simpara>You can install Red&#160;Hat Enterprise&#160;Linux on a large variety of storage devices. You can configure basic, locally accessible, storage devices in the <emphasis role="strong">Installation Destination</emphasis> window. Basic storage devices directly connected to the local system, such as hard disk drives and solid-state drives, are displayed in the <emphasis role="strong">Local Standard Disks</emphasis> section of the window.
 -On IBM Z, this section contains activated Direct Access Storage Devices (DASDs).</simpara>
 -<warning>
 -<simpara>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 <literal>/etc/dasd.conf</literal> configuration file of the system.</simpara>
 -</warning>
 +<simpara>You can install AlmaLinux on a large variety of storage devices. You can configure basic, locally accessible, storage devices in the <emphasis role="strong">Installation Destination</emphasis> window. Basic storage devices directly connected to the local system, such as hard disk drives and solid-state drives, are displayed in the <emphasis role="strong">Local Standard Disks</emphasis> section of the window.</simpara>
 <section xml:id="storage-devices-selection_storage-devices">
 <title>Storage device selection</title>
 <simpara>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 @@
 <varlistentry>
 <term>NVDIMM Devices</term>
 <listitem>
 -<simpara>Under specific circumstances, Red&#160;Hat Enterprise&#160;Linux 8.3 Beta can boot and run from (NVDIMM) devices in sector mode on the Intel 64 and AMD64 architectures.</simpara>
 -</listitem>
 -</varlistentry>
 -<varlistentry>
 -<term>System z Devices</term>
 -<listitem>
 -<simpara>Storage devices, or Logical Units (LUNs), attached through the zSeries Linux FCP (Fiber Channel Protocol) driver.</simpara>
 +<simpara>Under specific circumstances, AlmaLinux 8.3 can boot and run from (NVDIMM) devices in sector mode on the Intel 64 and AMD64 architectures.</simpara>
 </listitem>
 </varlistentry>
 </variablelist>
@@ -1220,7 +850,7 @@
 </listitem>
 <listitem>
 <simpara>Select the check box to enable the device that you require during the installation process.</simpara>
 -<simpara>Later in the installation process you can choose to install Red&#160;Hat Enterprise&#160;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.</simpara>
 +<simpara>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.</simpara>
 <note>
 <itemizedlist>
 <listitem>
@@ -1381,101 +1011,15 @@
 </listitem>
 </orderedlist>
 </section>
 -<section xml:id="configuring-dasd-storage-devices_storage-devices">
 -<title>Configuring DASD storage devices</title>
 -<simpara>Complete the following steps to configure DASD storage devices.</simpara>
 -<formalpara>
 -<title>Prerequisite</title>
 -<para>The <emphasis role="strong">Installation Summary</emphasis> window is open.</para>
 -</formalpara>
 -<orderedlist numeration="arabic">
 -<title>Procedure</title>
 -<listitem>
 -<simpara>From the <emphasis role="strong">Installation Summary</emphasis> window, click <emphasis role="strong">Installation Destination</emphasis>. The <emphasis role="strong">Installation Destination</emphasis> window opens, listing all available drives.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Under the <emphasis role="strong">Specialized &amp; Network Disks</emphasis> section, click <guibutton>Add a disk&#8230;</guibutton>. The storage devices selection window opens.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Click <guibutton>Add DASD</guibutton>. The <emphasis role="strong">Add DASD Storage Target</emphasis> dialog box opens and prompts you to specify a device number, such as <emphasis role="strong">0.0.0204</emphasis>, and attach additional DASDs that were not detected when the installation started.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Type the device number of the DASD that you want to attach in the <emphasis role="strong">Device number</emphasis> field.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Click <guibutton>Start Discovery</guibutton>.</simpara>
 -</listitem>
 -</orderedlist>
 -<note>
 -<itemizedlist>
 -<listitem>
 -<simpara>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 <guibutton>Done</guibutton>. The new DASDs are available for selection, marked as <literal>DASD device 0.0.<emphasis>xxxx</emphasis></literal> in the <emphasis role="strong">Local Standard Disks</emphasis> section of the <emphasis role="strong">Installation Destination</emphasis> window.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>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.</simpara>
 -</listitem>
 -</itemizedlist>
 -</note>
 -</section>
 -<section xml:id="configuring-fcp-devices_storage-devices">
 -<title>Configuring FCP devices</title>
 -<simpara>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.</simpara>
 -<itemizedlist>
 -<title>Prerequisites</title>
 -<listitem>
 -<simpara>The <emphasis role="strong">Installation Summary</emphasis> window is open.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>For an FCP-only installation, remove the <literal>DASD=</literal> option from the CMS configuration file or the <literal>rd.dasd=</literal> option from the parameter file to indicate that no DASD is present.</simpara>
 -</listitem>
 -</itemizedlist>
 -<orderedlist numeration="arabic">
 -<title>Procedure</title>
 -<listitem>
 -<simpara>From the <emphasis role="strong">Installation Summary</emphasis> window, click <emphasis role="strong">Installation Destination</emphasis>. The <emphasis role="strong">Installation Destination</emphasis> window opens, listing all available drives.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Under the <emphasis role="strong">Specialized &amp; Network Disks</emphasis> section, click <guibutton>Add a disk&#8230;</guibutton>. The storage devices selection window opens.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Click <guibutton>Add ZFCP LUN</guibutton>. The <emphasis role="strong">Add zFCP Storage Target</emphasis> dialog box opens allowing you to add a FCP (Fibre Channel Protocol) storage device.</simpara>
 -<simpara>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.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Type the 4 digit hexadecimal device number in the <emphasis role="strong">Device number</emphasis> field.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Type the 16 digit hexadecimal World Wide Port Number (WWPN) in the <emphasis role="strong">WWPN</emphasis> field.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Type the 16 digit hexadecimal FCP LUN identifier in the <emphasis role="strong">LUN</emphasis> field.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Click <guibutton>Start Discovery</guibutton> to connect to the FCP device.</simpara>
 -</listitem>
 -</orderedlist>
 -<simpara>The newly-added devices are displayed in the <emphasis role="strong">System z Devices</emphasis> tab of the <emphasis role="strong">Installation Destination</emphasis> window.</simpara>
 -<note>
 -<itemizedlist>
 -<listitem>
 -<simpara>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.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>Use only lower-case letters in hex values. If you enter an incorrect value and click <guibutton>Start Discovery</guibutton>, the installation program displays a warning. You can edit the configuration information and retry the discovery attempt.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>For more information about these values, consult the hardware documentation and check with your system administrator.</simpara>
 -</listitem>
 -</itemizedlist>
 -</note>
 -</section>
 +
 </section>
 +
 <section xml:id="installing-to-a-nvdimm-device_storage-devices">
 <title>Installing to an NVDIMM device</title>
 -<simpara>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&#160;Hat Enterprise&#160;Linux 8.3 Beta can boot and run from NVDIMM devices.</simpara>
 +<simpara>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.</simpara>
 <section xml:id="criteria-for-using-an-nvdimm-device-as-an-installation-target_installing-to-a-nvdimm-device">
 <title>Criteria for using an NVDIMM device as an installation target</title>
 -<simpara>You can install Red&#160;Hat Enterprise&#160;Linux&#160;8 to Non-Volatile Dual In-line Memory Module (NVDIMM) devices in sector mode on the Intel 64 and AMD64 architectures, supported by the <emphasis role="strong">nd_pmem</emphasis> driver.</simpara>
 +<simpara>You can install AlmaLinux&#160;8 to Non-Volatile Dual In-line Memory Module (NVDIMM) devices in sector mode on the Intel 64 and AMD64 architectures, supported by the <emphasis role="strong">nd_pmem</emphasis> driver.</simpara>
 <formalpara>
 <title>Conditions for using an NVDIMM device as storage</title>
 <para>To use an NVDIMM device as storage, the following conditions must be satisfied:</para>
@@ -1513,7 +1057,7 @@
 </section>
 <section xml:id="configuring-an-nvdimm-device-using-anaconda_installing-to-a-nvdimm-device">
 <title>Configuring an NVDIMM device using the graphical installation mode</title>
 -<simpara>A Non-Volatile Dual In-line Memory Module (NVDIMM) device must be properly configured for use by Red&#160;Hat Enterprise&#160;Linux 8.3 Beta using the graphical installation.</simpara>
 +<simpara>A Non-Volatile Dual In-line Memory Module (NVDIMM) device must be properly configured for use by AlmaLinux 8.3 using the graphical installation.</simpara>
 <warning>
 <simpara>Reconfiguration of a NVDIMM device process destroys any data stored on the device.</simpara>
 </warning>
@@ -1568,14 +1112,11 @@
 </chapter>
 <chapter xml:id="manual-partitioning_graphical-installation">
 <title>Configuring manual partitioning</title>
 -<simpara>You can use manual partitioning to configure your disk partitions and mount points and define the file system that Red&#160;Hat Enterprise&#160;Linux is installed on.</simpara>
 +<simpara>You can use manual partitioning to configure your disk partitions and mount points and define the file system that AlmaLinux is installed on.</simpara>
 <note>
 -<simpara>Before installation, you should consider whether you want to use partitioned or unpartitioned disk devices. For more information, see the Knowledgebase article at <link xl:href="https://access.redhat.com/solutions/163853">https://access.redhat.com/solutions/163853</link>.</simpara>
 -</note>
 -<simpara>An installation of Red&#160;Hat Enterprise&#160;Linux requires a minimum of one partition but Red&#160;Hat recommends using at least the following partitions or volumes: <literal>PReP</literal>, <literal>/</literal>, <literal>/home</literal>, <literal>/boot</literal>, and <literal>swap</literal>. You can also create additional partitions and volumes as you require.</simpara>
 -<note>
 -<simpara>An installation of Red&#160;Hat Enterprise&#160;Linux on IBM Power Systems servers requires a <literal>PReP</literal> boot partition.</simpara>
 +<simpara>Before installation, you should consider whether you want to use partitioned or unpartitioned disk devices.</simpara>
 </note>
 +<simpara>An installation of AlmaLinux requires a minimum of one partition but AlmaLinux recommends using at least the following partitions or volumes: <literal>PReP</literal>, <literal>/</literal>, <literal>/home</literal>, <literal>/boot</literal>, and <literal>swap</literal>. You can also create additional partitions and volumes as you require.</simpara>
 <warning>
 <simpara>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.</simpara>
 </warning>
@@ -1638,7 +1179,7 @@
 <simpara>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.</simpara>
 </listitem>
 <listitem>
 -<simpara>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&#160;Hat Enterprise&#160;Linux is LVM) and click the <emphasis role="strong">Click here to create them automatically</emphasis> link.</simpara>
 +<simpara>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 <emphasis role="strong">Click here to create them automatically</emphasis> link.</simpara>
 <simpara>A <literal>/boot</literal> partition, a <literal>/</literal> (root) volume, and a <literal>swap</literal> 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.</simpara>
 </listitem>
 </itemizedlist>
@@ -1689,14 +1230,11 @@
 </section>
 <section xml:id="configuring-a-mount-point-file-system_manual-partitioning">
 <title>Configuring a mount point file system</title>
 -<simpara>This procedure describes how to set the partitioning scheme for each mount point that was created manually. The available options are <literal>Standard Partition</literal>, <literal>LVM</literal>, and <literal>LVM Thin Provisioning</literal>.</simpara>
 +<simpara>This procedure describes how to set the partitioning scheme for each mount point that was created manually. The available options are <literal>Standard Partition</literal>, <literal>LVM</literal>, and <literal>LVM Thin Provisioning</literal>.</simpara>
 <note>
 <itemizedlist>
 <listitem>
 -<simpara>Btfrs support has been removed in Red&#160;Hat Enterprise&#160;Linux 8.3 Beta.</simpara>
 -</listitem>
 -<listitem>
 -<simpara>The <literal>/boot</literal> partition is always located on a standard partition, regardless of the value selected.</simpara>
 +<simpara>The <literal>/boot</literal> partition is always located on a standard partition, regardless of the value selected.</simpara>
 </listitem>
 </itemizedlist>
 </note>
@@ -1804,23 +1342,23 @@
 </section>
 <section xml:id="preserving-the-home-directory_manual-partitioning">
 <title>Preserving the /home directory</title>
 -<simpara>In a RHEL 8 graphical installation, you can preserve the <literal role="filename">/home</literal> directory that was used on your RHEL 7 system.</simpara>
 +<simpara>In a AlmaLinux 8 graphical installation, you can preserve the <literal role="filename">/home</literal> directory that was used on your RHEL-like 7 system.</simpara>
 <warning>
 -<simpara>Preserving <literal role="filename">/home</literal> is only possible if the <literal role="filename">/home</literal> directory is located on a separate <literal>/home</literal> partition on your RHEL 7 system.</simpara>
 +<simpara>Preserving <literal role="filename">/home</literal> is only possible if the <literal role="filename">/home</literal> directory is located on a separate <literal>/home</literal> partition on your RHEL-like 7 system.</simpara>
 </warning>
 -<simpara>Preserving the <literal role="filename">/home</literal> 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.</simpara>
 -<simpara>Complete this procedure to preserve the <literal role="filename">/home</literal> directory from your RHEL 7 system.</simpara>
 +<simpara>Preserving the <literal role="filename">/home</literal> 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.</simpara>
 +<simpara>Complete this procedure to preserve the <literal role="filename">/home</literal> directory from your RHEL-like 7 system.</simpara>
 <itemizedlist>
 <title>Prerequisites</title>
 <listitem>
 -<simpara>RHEL 7 system is installed on your computer.</simpara>
 +<simpara>RHEL-like 7 system is installed on your computer.</simpara>
 </listitem>
 <listitem>
 -<simpara>The <literal role="filename">/home</literal> directory is located on a separate <literal>/home</literal> partition on your RHEL 7 system.</simpara>
 +<simpara>The <literal role="filename">/home</literal> directory is located on a separate <literal>/home</literal> partition on your RHEL-like 7 system.</simpara>
 </listitem>
 <listitem>
 -<simpara>The RHEL 8 <literal>Installation Summary</literal> window is currently displayed.</simpara>
 +<simpara>The AlmaLinux 8 <literal>Installation Summary</literal> window is currently displayed.</simpara>
 </listitem>
 </itemizedlist>
 <orderedlist numeration="arabic">
@@ -1847,7 +1385,7 @@
 </figure>
 </listitem>
 <listitem>
 -<simpara>Optional: You can also customize various aspects of the <literal>/home</literal> partition required for your RHEL 8 system as described in <xref linkend="customizing-a-partition-or-volume_manual-partitioning"/>. However, to preserve <literal>/home</literal> from your RHEL 7 system, it is necessary to clear the <emphasis role="strong">Reformat</emphasis> check box.</simpara>
 +<simpara>Optional: You can also customize various aspects of the <literal>/home</literal> partition required for your AlmaLinux 8 system as described in <xref linkend="customizing-a-partition-or-volume_manual-partitioning"/>. However, to preserve <literal>/home</literal> from your RHEL-like 7 system, it is necessary to clear the <emphasis role="strong">Reformat</emphasis> check box.</simpara>
 </listitem>
 <listitem>
 <simpara>After you customized all partitions according to your requirements, click <guibutton>Done</guibutton>. The <emphasis role="strong">Summary of changes</emphasis> dialog box opens.</simpara>
@@ -1864,9 +1402,6 @@
 <title>Creating software RAID</title>
 <simpara>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.</simpara>
 <simpara>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.</simpara>
 -<note>
 -<simpara>On IBM Z, the storage subsystem uses RAID transparently. You do not have to configure software RAID manually.</simpara>
 -</note>
 <itemizedlist>
 <title>Prerequisites</title>
 <listitem>
@@ -1925,16 +1460,10 @@
 <listitem>
 <simpara>Click the <emphasis role="strong">Device Type</emphasis> drop-down menu and select <literal>LVM</literal>. The <emphasis role="strong">Volume Group</emphasis> drop-down menu is displayed with the newly-created volume group name.</simpara>
 <note>
 -<simpara>You cannot specify the size of the volume group&#8217;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 <literal role="command">vgcreate</literal> command, or use a Kickstart file with the <literal role="command">volgroup --pesize=<emphasis>size</emphasis></literal> command. See the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/performing_an_advanced_rhel_installation/index/"><emphasis>Performing an advanced RHEL installation</emphasis></link> document for more information about Kickstart.</simpara>
 +	<simpara>You cannot specify the size of the volume group&#8217;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 <literal role="command">vgcreate</literal> command, or use a Kickstart file with the <literal role="command">volgroup --pesize=<emphasis>size</emphasis></literal> command.</simpara>
 </note>
 </listitem>
 </orderedlist>
 -<itemizedlist>
 -<title>Additional resources</title>
 -<listitem>
 -<simpara>For more information about LVM, see the <emphasis><link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_and_managing_logical_volumes/index">Configuring and managing logical volumes</link></emphasis> document.</simpara>
 -</listitem>
 -</itemizedlist>
 </section>
 <section xml:id="configuring-lvm-logical-volume_manual-partitioning">
 <title>Configuring an LVM logical volume</title>
@@ -1954,7 +1483,7 @@
 <simpara>Click <guibutton>Modify</guibutton> to configure the newly-created volume group.</simpara>
 <simpara>The <emphasis role="strong">Configure Volume Group</emphasis> dialog box opens.</simpara>
 <note>
 -<simpara>You cannot specify the size of the volume group&#8217;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 <literal role="command">vgcreate</literal> command, or use a Kickstart file with the <literal role="command">volgroup --pesize=<emphasis>size</emphasis></literal> command. See the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/performing_an_advanced_rhel_installation/index/"><emphasis>Performing an advanced RHEL installation</emphasis></link> document for more information about Kickstart.</simpara>
 +	<simpara>You cannot specify the size of the volume group&#8217;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 <literal role="command">vgcreate</literal> command, or use a Kickstart file with the <literal role="command">volgroup --pesize=<emphasis>size</emphasis></literal> command.</simpara>
 </note>
 </listitem>
 <listitem>
@@ -2086,7 +1615,7 @@
 <simpara>Click <guibutton>Save Changes</guibutton> to apply the changes and return to the <emphasis role="strong">Configuration</emphasis> window.</simpara>
 </listitem>
 <listitem>
 -<simpara>When the installation process is complete, click <guibutton>Reboot</guibutton> to reboot and log in to your Red&#160;Hat Enterprise&#160;Linux 8.3 Beta system.</simpara>
 +<simpara>When the installation process is complete, click <guibutton>Reboot</guibutton> to reboot and log in to your AlmaLinux 8.3 system.</simpara>
 </listitem>
 </orderedlist>
 <informalexample>
@@ -2129,13 +1658,13 @@
 </orderedlist>
 </section>
 </chapter>
 -<part xml:id="installation-complete_installing-RHEL">
 +<part xml:id="installation-complete_installing-ALMA">
 <title>Completing the installation</title>
 <partintro>
 <simpara>Wait for the installation to complete. It might take a few minutes.</simpara>
 <simpara>After the installation is complete, remove any installation media if it is not ejected automatically upon reboot.</simpara>
 -<simpara>Red&#160;Hat Enterprise&#160;Linux&#160;8 starts after your system&#8217;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&#160;Hat, and more. If the X Window System is not installed, a <literal>login:</literal> prompt is displayed.</simpara>
 -<simpara>To learn how to complete initial setup, register, and secure your system, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/performing_a_standard_rhel_installation/post-installation-tasks_installing-rhel">Completing post-installation tasks</link> section of the <emphasis>Performing a standard RHEL installation</emphasis> document.</simpara>
 +<simpara>AlmaLinux&#160;8 starts after your system&#8217;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 <literal>login:</literal> prompt is displayed.</simpara>
 +<simpara></simpara>
 </partintro>
 </part>
 -</book>
 \ No newline at end of file
 +</book>
 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 @@
 -<section><para><emphasis role="bold">Help content for this screen is not yet available. See the installation instructions available online at <ulink url="https://access.redhat.com/">https://access.redhat.com/</ulink>.</emphasis></para></section>
 +<section><para><emphasis role="bold">Help content for this screen is not yet available. See the installation instructions available online at <ulink url="https://almalinux.org/">https://almalinux.org/</ulink>.</emphasis></para></section>
--- 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://access.redhat.com/documentation
 Version: 8.3.3
-Release: 1%{?dist}
+Release: 1%{?dist}.alma
 Epoch: 1
 BuildArch: noarch
@ -11,6 +11,7 @@ BuildArch: noarch
 # anaconda-user-help-x.x.x git tag.
 Source0: %{name}-%{version}.tar.gz
 Patch0:  anaconda-user-help-almalinux-branding.patch
 License: CC-BY-SA
@ -19,6 +20,7 @@ This package provides content for the Anaconda built-in help system.
 %prep
 %setup -q
 %patch0 -p1
 %install
 mkdir -p %{buildroot}%{_datadir}/anaconda/help