diff --git a/SOURCES/0001-Initial-debranding-for-MSVSphere.patch b/SOURCES/0001-Initial-debranding-for-MSVSphere.patch index 73c019e..b3639fe 100644 --- a/SOURCES/0001-Initial-debranding-for-MSVSphere.patch +++ b/SOURCES/0001-Initial-debranding-for-MSVSphere.patch @@ -1,14 +1,14 @@ -From 74239315a770a1c38730eacc1d66b9a2dfa4bfbc Mon Sep 17 00:00:00 2001 -From: Eugene Zamriy -Date: Sat, 1 Apr 2023 17:14:51 +0300 +From 87e66344291dde1f98bfa9d8c0ca963a29205461 Mon Sep 17 00:00:00 2001 +From: Sergey Cherevko +Date: Fri, 19 May 2023 10:50:34 +0300 Subject: [PATCH] Initial debranding for MSVSphere --- rhel/anaconda-gui.json | 6 +- - rhel/en-US/anaconda-help.xml | 476 ++++----------------------- + rhel/en-US/anaconda-help.xml | 522 ++++----------------------- rhel/en-US/rhel_help_placeholder.txt | 2 +- rhel/en-US/rhel_help_placeholder.xml | 2 +- - 4 files changed, 62 insertions(+), 424 deletions(-) + 4 files changed, 69 insertions(+), 463 deletions(-) diff --git a/rhel/anaconda-gui.json b/rhel/anaconda-gui.json index 79cc9c0..417f223 100644 @@ -34,32 +34,33 @@ index 79cc9c0..417f223 100644 "file": "anaconda-help.xml", "anchor": "network-hostname_configuring-system-settings" diff --git a/rhel/en-US/anaconda-help.xml b/rhel/en-US/anaconda-help.xml -index 28ee770..87c0fc1 100644 +index 91514ec..cc13c57 100644 --- a/rhel/en-US/anaconda-help.xml +++ b/rhel/en-US/anaconda-help.xml -@@ -2,18 +2,18 @@ +@@ -2,11 +2,11 @@ Customizing your installation - 2021-12-08 + 2023-01-24 -Red Hat +MSVSphere --<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 MSVSphere, you can customize location, software, and system settings and parameters, using the <emphasis role="strong">Installation Summary</emphasis> window.</simpara> +-<simpara role="_abstract">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 role="_abstract">When installing MSVSphere, 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> - <simpara><emphasis role="strong">LOCALIZATION</emphasis>: You can configure Keyboard, Language Support, and Time and Date.</simpara> - </listitem> + <variablelist> + <varlistentry> +@@ -18,7 +18,7 @@ + <varlistentry> + <term>SOFTWARE</term> <listitem> --<simpara><emphasis role="strong">SOFTWARE</emphasis>: You can configure Connect to Red Hat, Installation Source, and Software Selection.</simpara> -+<simpara><emphasis role="strong">SOFTWARE</emphasis>: You can configure Installation Source, and Software Selection.</simpara> +-<simpara>You can configure Connect to Red Hat, Installation Source, and Software Selection.</simpara> ++<simpara>You can configure Installation Source, and Software Selection.</simpara> </listitem> - <listitem> - <simpara><emphasis role="strong">SYSTEM</emphasis>: You can configure Installation Destination, KDUMP, Network and Host Name, and Security Policy.</simpara> -@@ -37,7 +37,7 @@ + </varlistentry> + <varlistentry> +@@ -49,7 +49,7 @@ <tbody> <row> <entry align="left" valign="top"><simpara>Yellow triangle with an exclamation mark and red text</simpara></entry> @@ -68,16 +69,31 @@ index 28ee770..87c0fc1 100644 </row> <row> <entry align="left" valign="top"><simpara>Grayed out and with a warning symbol (yellow triangle with an exclamation mark)</simpara></entry> -@@ -49,7 +49,7 @@ +@@ -61,39 +61,36 @@ <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 MSVSphere installation using the Graphical User Interface (GUI). The GUI is the preferred method of installing MSVSphere when you boot the system from a CD, DVD, or USB flash drive, or from a network using PXE.</simpara> </preface> - <chapter xml:id="installing-rhel-using-anaconda_graphical-installation"> +-<chapter xml:id="installing-rhel-using-anaconda_graphical-installation"> ++<chapter xml:id="installing-msvsphere-using-anaconda_graphical-installation"> <title>Configuring language and location settings -@@ -69,19 +69,19 @@ + The installation program uses the language that you selected during installation. + + Prerequisites + +-You created installation media. See Creating a bootable DVD or CD ++You specified an installation source if you are using the Boot ISO image file. + + +-You specified an installation source if you are using the Boot ISO image file. See Preparing an installation source +- +- +-You booted the installation. See Booting the installer ++You booted the installation. + + Procedure @@ -92,8 +108,7 @@ index 28ee770..87c0fc1 100644 +From the right-hand pane of the Welcome to MSVSphere window, select a location specific to your region. --Click Continue to proceed to the Installing and deploying RHEL on the Red Hat Customer Portal window. -+Click Continue to proceed to the Installing and deploying MSVSphere. + Click Continue to proceed to the Graphical installations 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. @@ -101,55 +116,59 @@ index 28ee770..87c0fc1 100644 To continue with the installation, click I want to proceed, or -@@ -136,7 +136,7 @@ To change any of the settings, complete the following steps, otherwise proceed t +@@ -106,9 +103,6 @@ + + + Additional resources +- +-Configuring localization settings +- + + + +@@ -119,8 +113,7 @@ + + + Configuring keyboard, language, and time and date settings +-Keyboard, Language, and Time and Date Settings are configured by default as part of Installing RHEL using Anaconda. +-To change any of the settings, complete the following steps, otherwise proceed to Configuring software settings. ++Keyboard, Language, and Time and Date Settings are configured by default as part of Installing MSVSphere using Anaconda. - + + Procedure +@@ -128,7 +121,7 @@ To change any of the settings, complete the following steps, otherwise proceed t + Configure keyboard settings: + --Click Done to apply the settings and return to Installing and deploying RHEL on the Red Hat Customer Portal. -+Click Done to apply the settings and return to Installing and deploying MSVSphere. - - - -@@ -150,7 +150,7 @@ To change any of the settings, complete the following steps, otherwise proceed t - From the left pane, click a group to select additional languages, and from the right pane, select regional options. Repeat this process for languages that you require. +-From the Installation Summary window, click Keyboard. The default layout depends on the option selected in Installing RHEL using Anaconda. ++From the Installation Summary window, click Keyboard. The default layout depends on the option selected in Installing MSVSphere using Anaconda. --Click Done to apply the changes and return to Installing and deploying RHEL on the Red Hat Customer Portal. -+Click Done to apply the changes and return to Installing and deploying MSVSphere. - - - -@@ -161,7 +161,7 @@ To change any of the settings, complete the following steps, otherwise proceed t + Click + to open the Add a Keyboard Layout window and change to a different layout. +@@ -173,8 +166,8 @@ To change any of the settings, complete the following steps, otherwise proceed t + 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 Time & Date settings are configured by default based on the settings you selected in Installing RHEL using Anaconda. -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 Installing MSVSphere using Anaconda. +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). MSVSphere can not add cities or regions to this database. You can find more information at the IANA official website. -@@ -180,7 +180,7 @@ To change any of the settings, complete the following steps, otherwise proceed t - - - --Click Done to apply the changes and return to Installing and deploying RHEL on the Red Hat Customer Portal. -+Click Done to apply the changes and return to Installing and deploying MSVSphere. - - If you disable network time synchronization, the controls at the bottom of the window become active, allowing you to set the time and date manually. - -@@ -195,9 +195,9 @@ To change any of the settings, complete the following steps, otherwise proceed t +@@ -207,9 +200,9 @@ To change any of the settings, complete the following steps, otherwise proceed t 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 MSVSphere 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 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 MSVSphere 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 MSVSphere as a second system, or if you are upgrading a previous release of MSVSphere. 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. -@@ -207,10 +207,10 @@ To change any of the settings, complete the following steps, otherwise proceed t +@@ -219,10 +212,10 @@ To change any of the settings, complete the following steps, otherwise proceed t If you choose to partition your system automatically, you should manually edit your /boot partition. @@ -162,7 +181,7 @@ index 28ee770..87c0fc1 100644 -@@ -226,7 +226,7 @@ If you choose to partition your system automatically, you should manually edit y +@@ -238,7 +231,7 @@ If you choose to partition your system automatically, you should manually edit y 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. @@ -171,7 +190,12 @@ index 28ee770..87c0fc1 100644 -@@ -256,7 +256,7 @@ If you choose to partition your system automatically, you should manually edit y +@@ -265,11 +258,11 @@ If you choose to partition your system automatically, you should manually edit y + Optional: Under Storage Configuration, select the Automatic radio button. + + Automatic partitioning is the recommended method of partitioning your storage. +-You can also configure custom partitioning, for more details see Configuring manual partitioning ++You can also configure custom partitioning @@ -180,16 +204,24 @@ index 28ee770..87c0fc1 100644 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. -@@ -270,7 +270,7 @@ If you choose to partition your system automatically, you should manually edit y +@@ -283,7 +276,7 @@ If you choose to partition your system automatically, you should manually edit y 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. See the Performing an advanced RHEL 9 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. -@@ -287,7 +287,7 @@ If you choose to partition your system automatically, you should manually edit y +@@ -292,7 +285,6 @@ If you choose to partition your system automatically, you should manually edit y + + + Optional: Click the Full disk summary and bootloader link in the lower left-hand side of the window to select which storage device contains the boot loader. +-For more information, see Boot loader installation. + + In most cases it is sufficient to leave the boot loader in the default location. Some configurations, for example, systems that require chain loading from another boot loader require the boot drive to be specified manually. + +@@ -301,7 +293,7 @@ If you choose to partition your system automatically, you should manually edit y Click Done. @@ -198,7 +230,7 @@ index 28ee770..87c0fc1 100644 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. -@@ -298,11 +298,11 @@ If you choose to partition your system automatically, you should manually edit y +@@ -312,12 +304,9 @@ If you choose to partition your system automatically, you should manually edit y 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. @@ -206,18 +238,18 @@ index 28ee770..87c0fc1 100644 +Alternatively, you can click Delete all, this deletes all existing partitions on all disks and makes this space available to MSVSphere. Existing data on all disks is lost. - --Click Reclaim space to apply the changes and return to Installing and deploying RHEL on the Red Hat Customer Portal. -+Click Reclaim space to apply the changes and return to Installing and deploying MSVSphere. - +- +-Click Reclaim space to apply the changes and return to Graphical installations. +- -@@ -313,13 +313,13 @@ If you choose to partition your system automatically, you should manually edit y + +@@ -333,13 +322,13 @@ If you choose to partition your system automatically, you should manually edit y
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. -+MSVSphere 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. +-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 64-bit IBM Z, the zipl boot loader is used. ++MSVSphere uses GRand Unified Bootloader version 2 (GRUB2) as the boot loader for AMD64 and Intel 64, IBM Power Systems, and ARM. For 64-bit IBM Z, the zipl boot loader is used. 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. @@ -229,38 +261,65 @@ index 28ee770..87c0fc1 100644 Procedure -@@ -358,7 +358,7 @@ If you choose to partition your system automatically, you should manually edit y - +@@ -377,9 +366,6 @@ If you choose to partition your system automatically, you should manually edit y - --Click Done to apply the settings and return to Installing and deploying RHEL on the Red Hat Customer Portal. -+Click Done to apply the settings and return to Installing and deploying MSVSphere. + +- +-Click Done to apply the settings and return to Graphical installations. +- -@@ -384,7 +384,7 @@ If you choose to partition your system automatically, you should manually edit y + 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. +@@ -404,7 +390,7 @@ If you choose to partition your system automatically, you should manually edit y --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. 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. -@@ -493,7 +493,7 @@ If you choose to partition your system automatically, you should manually edit y +@@ -432,7 +418,7 @@ If you choose to partition your system automatically, you should manually edit y + The host name can either be a fully qualified domain name (FQDN) in the format hostname.domainname, or a short host name without the domain. 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 system, specify only the short host name. + + +-When using static IP and host name configuration, it depends on the planned system use case whether to use a short name or FQDN. Red Hat Identity Management configures FQDN during provisioning but some 3rd party software products may require short name. In either case, to ensure availability of both forms in all situations, add an entry for the host in /etc/hosts` in the format IP FQDN short-alias. ++When using static IP and host name configuration, it depends on the planned system use case whether to use a short name or FQDN. MSVSphere Identity Management configures FQDN during provisioning but some 3rd party software products may require short name. In either case, to ensure availability of both forms in all situations, add an entry for the host in /etc/hosts` in the format IP FQDN short-alias. + + + The value localhost 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. +@@ -471,7 +457,7 @@ If you choose to partition your system automatically, you should manually edit y + + + Team: NIC Teaming, a new implementation to aggregate links, designed to provide a small kernel driver to implement the fast handling of packet flows, and various applications to do everything else in user space. +-Network teaming is deprecated in Red Hat Enterprise Linux 9. Consider using the network bonding driver as an alternative. For details, see Configuring network bonding. ++Network teaming is deprecated in MSVSphere 9. Consider using the network bonding driver as an alternative. + + + Vlan (Virtual LAN): A method to create multiple distinct broadcast domains which are mutually isolated. +@@ -481,7 +467,6 @@ If you choose to partition your system automatically, you should manually edit y + + + Select the interface type and click Add. An editing interface dialog box opens, allowing you to edit any available settings for your chosen interface type. +-For more information see Editing network interface. + + + Click Save to confirm the virtual interface settings and return to the Network & Host name window. +@@ -521,7 +506,7 @@ If you choose to partition your system automatically, you should manually edit y --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. For further information about NetworkManager, including the nm-connection-editor tool. +-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. -@@ -569,365 +569,17 @@ If you choose to partition your system automatically, you should manually edit y +@@ -597,373 +582,17 @@ If you choose to partition your system automatically, you should manually edit y Additional resources --To learn more about network configuration after installation, see the Configuring and managing networking document. +-Configuring and managing networking - - -
@@ -282,7 +341,7 @@ index 28ee770..87c0fc1 100644 - -
-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 9 system, and ensure that the entitlement server auto-attaches the most appropriate subscription to your system. +-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 9 system, and ensure that the entitlement server auto-attaches the most appropriate subscription to your system. -Benefits include: - - @@ -306,6 +365,9 @@ index 28ee770..87c0fc1 100644 - -During a Kickstart installation when using Kickstart automation scripts - +- +-After installation using the subscription-manager 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. - @@ -352,22 +414,22 @@ index 28ee770..87c0fc1 100644 - - - -- +- -Additional resources - --For more information about Image Builder, see the Composing a customized RHEL system image document. +-Composing a customized RHEL system image - - --For more information about Kickstart, see the Performing an advanced RHEL installation document. +-Performing an advanced RHEL 9 installation - - --For more information about Subscription Manager, see the Using and Configuring Red Hat Subscription Manager document. +-Using and Configuring Red Hat Subscription Manager - - -
-
-Configuring Connect to Red Hat options --Use the following procedure to configure the Connect to Red Hat options in the GUI. +-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. - @@ -410,11 +472,14 @@ index 28ee770..87c0fc1 100644 -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. +-If you are running Satellite Server or performing internal testing, select the Satellite 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. +-RHEL 9 is supported only with Satellite 6.11 or later. Check the version prior attempting to register the system. +- +- +-The Satellite 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. @@ -442,7 +507,7 @@ index 28ee770..87c0fc1 100644 -
-
-Installation source repository after system registration --The installation source repository used after system registration is dependent on how the system was booted. +-The installation source repository used after system registration is dependent on how the system was booted. - - -System booted from the Boot ISO or the DVD ISO image file @@ -470,14 +535,14 @@ index 28ee770..87c0fc1 100644 -
-
-Verifying your system registration from the CDN --Use this procedure to verify that your system is registered to the CDN using the GUI. +-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 Installing and deploying RHEL on the Red Hat Customer Portal and Registered is displayed under Connect to Red Hat on the Installation Summary window. +-You have completed the registration process as documented in the Register and install from CDN using GUI and Registered is displayed under Connect to Red Hat on the Installation Summary window. - - - @@ -521,13 +586,13 @@ index 28ee770..87c0fc1 100644 - -Additional resources - --See Simple Content Access. +-Simple Content Access - - -
-
-Unregistering your system from the CDN --Use this procedure to unregister your system from the CDN using the GUI. +-Use this procedure to unregister your system from the CDN using the GUI. - - - @@ -549,7 +614,7 @@ index 28ee770..87c0fc1 100644 - -Prerequisite - --You have completed the registration process as documented in the Installing and deploying RHEL on the Red Hat Customer Portal and Registered is displayed under Connect to Red Hat on the Installation Summary window. +-You have completed the registration process as documented in the Registering and installing RHEL from the CDN and Registered is displayed under Connect to Red Hat on the Installation Summary window. - - - @@ -599,8 +664,10 @@ index 28ee770..87c0fc1 100644 - -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 +-
+-
+-Additional resources +- - -For information about Red Hat Insights, see the Red Hat Insights product documentation. - @@ -615,48 +682,58 @@ index 28ee770..87c0fc1 100644
- Configuring Security Policy --This section contains information about the Red Hat Enterprise Linux 9 security policy and how to configure it for use on your system. -+This section contains information about the MSVSphere 9 security policy and how to configure it for use on your system. + Installing System Aligned with a Security Policy +-This section contains information about applying Red Hat Enterprise Linux 9 security policy during installation and how to configure it for use on your system before the first boot. ++This section contains information about applying MSVSphere 9 security policy during installation and how to configure it for use on your system before the first boot.
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 MSVSphere 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. -
-
-@@ -981,9 +633,6 @@ A separate window opens allowing you to enter a URL for valid security content.< +-The Red Hat Enterprise Linux includes OpenSCAP suite to enable automated configuration of the system in alignment with a particular security policy. The policy is implemented using the Security Content Automation Protocol (SCAP) standard. The packages are available in the AppStream repository. However, by default, the installation and post-installation process does not enforce any policies and therefore does not involve any checks unless specifically configured. ++The MSVSphere includes OpenSCAP suite to enable automated configuration of the system in alignment with a particular security policy. The policy is implemented using the Security Content Automation Protocol (SCAP) standard. The packages are available in the AppStream repository. However, by default, the installation and post-installation process does not enforce any policies and therefore does not involve any checks 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 and scap-security-guide packages are added to your package selection, providing a preinstalled tool for compliance and vulnerability scanning. + When you select a security policy, the Anaconda GUI installer requires the configuration to adhere to the policy’s requirements. There might be conflicting package selections, as well as separate partitions defined. Only after all the requirements are met, you can start the installation. + At the end of the installation process, the selected OPenSCAP security policy automatically hardens the system and scans it to verify compliance, saving the scan results to the /root/openscap_data directory on the installed system. +@@ -1019,9 +648,6 @@ A separate window opens allowing you to enter a URL for valid security content.< 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. +-Red Hat Enterprise Linux security compliance information is available in the Security hardening document. -
-@@ -993,9 +642,9 @@ A separate window opens allowing you to enter a URL for valid security content.< +@@ -1031,17 +657,17 @@ A separate window opens allowing you to enter a URL for valid security content.< 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. +-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 MSVSphere Server DVD configures the source as local media. Prerequisites -@@ -1028,7 +677,7 @@ A separate window opens allowing you to enter a URL for valid security content.< + +-You have downloaded the full installation image. Downloading a RHEL installation ISO image ++You have downloaded the full installation image. + + +-You have created a bootable physical media. Creating a bootable CD or DVD ++You have created a bootable physical media. + + + The Installation Summary window is open. +@@ -1066,7 +692,7 @@ A separate window opens allowing you to enter a URL for valid security content.< 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 Linux9 installation. +-Do not disable the AppStream repository check box if you want a full Red Hat Enterprise Linux 9 installation. +Do not disable the AppStream repository check box if you want a full MSVSphere 9 installation. -@@ -1036,9 +685,6 @@ A separate window opens allowing you to enter a URL for valid security content.< +@@ -1074,18 +700,9 @@ A separate window opens allowing you to enter a URL for valid security content.< @@ -666,43 +743,57 @@ index 28ee770..87c0fc1 100644 Optional: Select the On the network option to download and install packages from a network location instead of local media. -@@ -1116,15 +762,14 @@ A separate window opens allowing you to enter a URL for valid security content.< +- +-If you do not want to download and install additional repositories from a network location, proceed to Configuring software selection. +- +- +-This option is available only when a network connection is active. See Configuring network and host name options for information about how to configure network connections in the GUI. +- + + + +@@ -1154,18 +771,17 @@ A separate window opens allowing you to enter a URL for valid security content.< 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, MSVSphere recommends that you select the Minimal Install base environment. Minimal install installs a basic version of MSVSphere 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. +-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 DNF package manager to install additional software. +-For more information about DNF package manager, see the Configuring basic system settings document. ++If you are unsure about which packages to install, MSVSphere recommends that you select the Minimal Install base environment. Minimal install installs a basic version of MSVSphere 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 DNF 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. +-The dnf group list command lists all package groups from dnf repositories. See the Configuring basic system settings document for more information. ++The dnf group list command lists all package groups from dnf 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. See the Performing an advanced RHEL 9 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. - - - -@@ -1155,14 +800,14 @@ For more information about Yum package manager, see the Additional Software for Selected Environment pane, select one or more options. --Click Done to apply the settings and return to Installing and deploying RHEL on the Red Hat Customer Portal. -+Click Done to apply the settings and return to Installing and deploying MSVSphere. +-By default, RHEL 9 does not install the TuneD package. You can manually install the TuneD package using the dnf install tuned command. ++By default, MSVSphere 9 does not install the TuneD package. You can manually install the TuneD package using the dnf install tuned command. - -
+ + +@@ -1203,7 +819,7 @@ For more information about DNF package manager, see the 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. +You can install MSVSphere 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). + On 64-bit 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. -@@ -1399,10 +1044,10 @@ If discovery succeeds, the Add iSCSI Storage Target window di +@@ -1413,7 +1029,7 @@ If discovery succeeds, the Add iSCSI Storage Target window di + Type the 4 digit hexadecimal device number in the Device number field. + + +-When installing RHEL-9.0 or older releases or if the zFCP device is not configured in NPIV mode, or when auto LUN scanning is disabled by the zfcp.allow_lun_scan=0 kernel module parameter, provide the following values: ++When installing MSVSphere 9 or older releases or if the zFCP device is not configured in NPIV mode, or when auto LUN scanning is disabled by the zfcp.allow_lun_scan=0 kernel module parameter, provide the following values: + + + Type the 16 digit hexadecimal World Wide Port Number (WWPN) in the WWPN field. +@@ -1445,10 +1061,10 @@ If discovery succeeds, the Add iSCSI Storage Target window di
Installing to an NVDIMM device @@ -710,35 +801,36 @@ index 28ee770..87c0fc1 100644 +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, MSVSphere 9 can boot and run from NVDIMM devices.
Criteria for using an NVDIMM device as an installation target --You can install Red Hat Enterprise Linux 9 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 MSVSphere 9 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 Red Hat Enterprise Linux 9 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 MSVSphere 9 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: -@@ -1440,7 +1085,7 @@ If discovery succeeds, the Add iSCSI Storage Target window di +@@ -1486,7 +1102,7 @@ If discovery succeeds, the Add iSCSI Storage Target window di
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 9 using the graphical installation. -+A Non-Volatile Dual In-line Memory Module (NVDIMM) device must be properly configured for use by MSVSphere 9 using the graphical installation. +-A Non-Volatile Dual In-line Memory Module (NVDIMM) device must be properly configured for use by Red Hat Enterprise Linux 9 using the graphical installation. ++A Non-Volatile Dual In-line Memory Module (NVDIMM) device must be properly configured for use by MSVSphere 9 using the graphical installation. Reconfiguration of a NVDIMM device process destroys any data stored on the device. -@@ -1495,11 +1140,11 @@ If discovery succeeds, the Add iSCSI Storage Target window di +@@ -1541,11 +1157,11 @@ If discovery succeeds, the Add iSCSI Storage Target window di 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 MSVSphere 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. +-Before installation, you should consider whether you want to use partitioned or unpartitioned disk devices. For more information on the advantages and disadvantages to using partitioning on LUNs, either directly or with LVM, see the article at https://access.redhat.com/solutions/163853. ++Before installation, you should consider whether you want to use partitioned or unpartitioned disk devices. -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: /, /home, /boot, and swap. You can also create additional partitions and volumes as you require. -+An installation of MSVSphere requires a minimum of one partition but Red Hat recommends using at least the following partitions or volumes: /, /home, /boot, and swap. You can also create additional partitions and volumes as you require. ++An installation of MSVSphere requires a minimum of one partition but MSVSphere recommends using at least the following partitions or volumes: /, /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. -@@ -1562,7 +1207,7 @@ If discovery succeeds, the Add iSCSI Storage Target window di +@@ -1608,7 +1224,7 @@ If discovery succeeds, the Add iSCSI Storage Target window di 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. @@ -747,7 +839,7 @@ index 28ee770..87c0fc1 100644 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. -@@ -1617,7 +1262,7 @@ If discovery succeeds, the Add iSCSI Storage Target window di +@@ -1663,7 +1279,7 @@ If discovery succeeds, the Add iSCSI Storage Target window di @@ -756,31 +848,31 @@ index 28ee770..87c0fc1 100644 The /boot partition is always located on a standard partition, regardless of the value selected. -@@ -1719,23 +1364,23 @@ If discovery succeeds, the Add iSCSI Storage Target window di +@@ -1765,23 +1381,23 @@ If discovery succeeds, the Add iSCSI Storage Target window di
Preserving the /home directory --In a Red Hat Enterprise Linux 9 graphical installation, you can preserve the /home directory that was used on your RHEL 7 system. -+In a MSVSphere 9 graphical installation, you can preserve the /home directory that was used on your EL 7 system. +-In a Red Hat Enterprise Linux 9 graphical installation, you can preserve the /home directory that was used on your RHEL 8 system. ++In a MSVSphere 9 graphical installation, you can preserve the /home directory that was used on your EL 8 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 EL 7 system. +-Preserving /home is only possible if the /home directory is located on a separate /home partition on your RHEL 8 system. ++Preserving /home is only possible if the /home directory is located on a separate /home partition on your EL 8 system. --Preserving the /home directory that includes various configuration settings, makes it possible that the GNOME Shell environment on the new Red Hat Enterprise Linux 9 system is set in the same way as it was on your RHEL 7 system. --Note that this applies only for users on Red Hat Enterprise Linux 9 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 MSVSphere 9 system is set in the same way as it was on your EL 7 system. -+Note that this applies only for users on MSVSphere 9 with the same user name and ID as on the previous EL 7 system. -+Complete this procedure to preserve the /home directory from your EL 7 system. +-Preserving the /home directory that includes various configuration settings, makes it possible that the GNOME Shell environment on the new Red Hat Enterprise Linux 9 system is set in the same way as it was on your RHEL 8 system. +-Note that this applies only for users on Red Hat Enterprise Linux 9 with the same user name and ID as on the previous RHEL 8 system. +-Complete this procedure to preserve the /home directory from your RHEL 8 system. ++Preserving the /home directory that includes various configuration settings, makes it possible that the GNOME Shell environment on the new MSVSphere 9 system is set in the same way as it was on your EL 8 system. ++Note that this applies only for users on MSVSphere 9 with the same user name and ID as on the previous EL 8 system. ++Complete this procedure to preserve the /home directory from your EL 8 system. Prerequisites --RHEL 7 system is installed on your computer. -+EL 7 system is installed on your computer. +-RHEL 8 system is installed on your computer. ++EL 8 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 EL 7 system. +-The /home directory is located on a separate /home partition on your RHEL 8 system. ++The /home directory is located on a separate /home partition on your EL 8 system. -The Red Hat Enterprise Linux 9 Installation Summary window is currently displayed. @@ -788,50 +880,58 @@ index 28ee770..87c0fc1 100644 -@@ -1753,7 +1398,7 @@ Note that this applies only for users on Red Hat Enterprise Linux 9 wi +@@ -1799,7 +1415,7 @@ Note that this applies only for users on Red Hat Enterprise Linux 9 wi Choose the /home partition, fill in /home under Mount Point: and clear the Reformat check box. --Optional: You can also customize various aspects of the /home partition required for your Red Hat Enterprise Linux 9 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 MSVSphere 9 system as described in . However, to preserve /home from your EL 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 Red Hat Enterprise Linux 9 system as described in Customizing a mount point file system. However, to preserve /home from your RHEL 8 system, it is necessary to clear the Reformat check box. ++. Optional: You can also customize various aspects of the /home partition required for your MSVSphere 9 system as described in Customizing a mount point file system. However, to preserve /home from your EL 8 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. -@@ -1813,7 +1458,7 @@ Note that this applies only for users on Red Hat Enterprise Linux 9 wi - +@@ -1860,9 +1476,6 @@ Note that this applies only for users on Red Hat Enterprise Linux 9 wi - A message is displayed at the bottom of the window if the specified RAID level requires more disks. --To learn more about soft corruption and how you can protect your data when configuring a RAID LV, see Using DM integrity with RAID LV. -+To learn more about soft corruption and how you can protect your data when configuring a RAID LV. + + Additional resources +- +-Creating a RAID LV with DM integrity +- +
- Creating an LVM logical volume -@@ -1832,15 +1477,12 @@ Note that this applies only for users on Red Hat Enterprise Linux 9 wi +@@ -1882,15 +1495,12 @@ Note that this applies only for users on Red Hat Enterprise Linux 9 wi 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. See the Performing an advanced RHEL 9 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 and managing logical volumes -
-@@ -1861,7 +1503,7 @@ Note that this applies only for users on Red Hat Enterprise Linux 9 wi +@@ -1911,7 +1521,7 @@ Note that this applies only for users on Red Hat Enterprise Linux 9 wi 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. See the Performing an advanced RHEL 9 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. +@@ -2098,4 +1708,4 @@ Note that this applies only for users on Red Hat Enterprise Linux 9 wi + + + +- +\ No newline at end of file ++ diff --git a/rhel/en-US/rhel_help_placeholder.txt b/rhel/en-US/rhel_help_placeholder.txt index 5c5bd51..54e7ad1 100644 --- a/rhel/en-US/rhel_help_placeholder.txt diff --git a/SPECS/anaconda-user-help.spec b/SPECS/anaconda-user-help.spec index 8c8506b..5305615 100644 --- a/SPECS/anaconda-user-help.spec +++ b/SPECS/anaconda-user-help.spec @@ -32,6 +32,10 @@ cp -r * %{buildroot}%{_datadir}/anaconda/help/ %{_datadir}/anaconda/help/* %changelog +* Fri May 19 2023 Sergey Cherevko - 9.2.1-1.inferit +- Debranding for MSVSphere +- Rebuilt for MSVSphere 9.2 + * Sat Apr 01 2023 Eugene Zamriy - 9.0.0-1.inferit - Initial debranding for MSVSphere - Rebuilt for MSVSphere 9.1