mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 34. Desktop Broken pygobject3 package dependencies prevent upgrade from Red Hat Enterprise Linux 7.1 The pygobject3-devel.i686 32-bit package has been removed in Red Hat Enterprise Linux 7.2 and was replaced with a multilib version. If you have the 32-bit version of the package installed on a Red Hat Enterprise Linux 7.1 system, then you will encounter a yum error when attempting to upgrade to Red Hat Enterprise Linux 7.2. To work around this problem, use the yum remove pygobject3-devel.i686 command as root to uninstall the 32-bit version of the package before upgrading your system. Build requirements not defined correctly for Emacs The binutils package earlier than version 2.23.52.0.1-54 causes a segmentation fault during the build. As a consequence, it is not possible to build the Emacs text editor on IBM Power Systems. To work around this problem, install the latest binutils . External display issues when combining laptop un/dock and suspend In the GNOME desktop environment, with some laptops, external displays connected to a docking station might not be automatically activated when resuming a suspended laptop after it has been undocked and docked again. To work around this problem, open the Displays configuration panel or run the xrandr command in a terminal. This makes the external displays available again. Emacs sometimes terminates unexpectedly when using the up arrow on ARM On the ARM architecture, the Emacs text editor sometimes terminates unexpectedly with a segmentation fault when scrolling up a file buffer. This happens only when the syntax highlighting is enabled. There is not currently any known workaround for this problem.

Commands:
Chapter 48. Security USBGuard enables blocking USB devices while the screen is locked as a Technology Preview With the USBGuard framework, you can influence how an already running usbguard-daemon instance handles newly inserted USB devices by setting the value of the InsertedDevicePolicy runtime parameter. This functionality is provided as a Technology Preview, and the default choice is to apply the policy rules to figure out whether to authorize the device or not. See the Blocking USB devices while the screen is locked Knowledge Base article: https://access.redhat.com/articles/3230621 (BZ#1480100) pk12util can now import certificates signed with RSA-PSS The pk12util tool now provides importing a certificate signed with the RSA-PSS algorithm as a Technology Preview. Note that if the corresponding private key is imported and has the PrivateKeyInfo.privateKeyAlgorithm field that restricts the signing algorithm to RSA-PSS , it is ignored when importing the key to a browser. See https://bugzilla.mozilla.org/show_bug.cgi?id=1413596 for more information. (BZ# 1431210 ) Support for certificates signed with RSA-PSS in certutil has been improved Support for certificates signed with the RSA-PSS algorithm in the certutil tool has been improved. Notable enhancements and fixes include: The --pss option is now documented. The PKCS#1 v1.5 algorithm is no longer used for self-signed signatures when a certificate is restricted to use RSA-PSS . Empty RSA-PSS parameters in the subjectPublicKeyInfo field are no longer printed as invalid when listing certificates. The --pss-sign option for creating regular RSA certificates signed with the RSA-PSS algorithm has been added. Support for certificates signed with RSA-PSS in certutil is provided as a Technology Preview. (BZ# 1425514 ) NSS is now able to verify RSA-PSS signatures on certificates With the new version of the nss package, the Network Security Services (NSS) libraries now provide verifying RSA-PSS signatures on certificates as a Technology Preview. Prior to this update, clients using NSS as the SSL backend were not able to establish a TLS connection to a server that offered only certificates signed with the RSA-PSS algorithm. Note that the functionality has the following limitations: The algorithm policy settings in the /etc/pki/nss-legacy/rhel7.config file do not apply to the hash algorithms used in RSA-PSS signatures. RSA-PSS parameters restrictions between certificate chains are ignored and only a single certificate is taken into account. (BZ# 1432142 ) SECCOMP can be now enabled in libreswan As a Technology Preview, the seccomp=enabled|tolerant|disabled option has been added to the ipsec.conf configuration file, which makes it possible to use the Secure Computing mode (SECCOMP). This improves the syscall security by whitelisting all the system calls that Libreswan is allowed to execute. For more information, see the ipsec.conf(5) man page. (BZ# 1375750 )

Commands:
2.8. Installing GFS Installing GFS consists of installing Red Hat GFS RPMs on nodes in a Red Hat cluster. Before installing the RPMs, make sure of the following: The cluster nodes meet the system requirements described in this chapter. You have noted the key characteristics of your GFS configuration (refer to Section 1.4, "Before Setting Up GFS" ). The correct Red Hat Cluster Suite software is installed in the cluster. For information on installing RPMS for Red Hat Cluster Suite and Red Hat GFS, see Configuring and Managing a Red Hat Cluster . If you have already installed the appropriate Red Hat Cluster Suite RPMs, follow the procedures that pertain to installing the Red Hat GFS RPMs.

Commands:
Chapter 4. Deprecated and unsupported Red Hat build of OpenJDK capabilities Ensure that you review the following deprecated and unsupported features before you install Red Hat build of OpenJDK 21: JDK Mission Control in the Red Hat build of OpenJDK 21 for Windows packages The Windows installer and the zip archive for Red Hat build of OpenJDK 21 no longer provide a distribution of JDK Mission Control (JMC). You can use the Red Hat build of Cryostat to manage JFR recordings for Java applications deployed on cloud platforms such as Red Hat OpenShift . For more information about the removal of JMC, see the Red Hat knowledge base article: Where is JDK Mission Control (JMC) in JDK 21? . Deprecate Finalization for removal This release deprecates Finalization for removal in a future release. For more information, see JEP 421: Deprecate Finalization for Removal . Prepare to disallow the dynamic loading of agents This release issues warnings when agents are loaded dynamically into a running JVM. The dynamic loading of agents will be disallowed by default in a future release. For more information, see JEP 451: Prepare to Disallow the Dynamic Loading of Agents . Note Red Hat does not provide builds of OpenJDK with 32-bit support. In OpenJDK 21, Windows 32-bit x86 support is also now deprecated upstream. This feature will be removed in a future release. For more information, see JEP 449: Deprecate the Windows 32-bit x86 Port for Removal .

Commands:
Chapter 4. Adding Red Hat integrations to the Hybrid Cloud Console You can connect your Red Hat OpenShift Container Platform environment to the Red Hat Hybrid Cloud Console as a cloud integration, so that the cost management service on the Hybrid Cloud Console can use data from your environment to track your cloud costs. You can use the cost management service to perform financially related tasks, such as: Visualizing, understanding, and analyzing the use of resources and costs Forecasting your future consumption and comparing them with budgets Optimizing resources and consumption Identifying patterns of usage for further analysis Integrating with third-party tools that can benefit from cost and resourcing data Note For Red Hat OpenShift Container Platform 4.6 and later, install the costmanagement-metrics-operator from the OpenShift Container Platform web console. For more information, see Integrating OpenShift Container Platform data into cost management . 4.1. Adding an OpenShift Container Platform integration You can connect your Red Hat OpenShift Container Platform environment to the Red Hat Hybrid Cloud Console as an integration so that you can use OpenShift Container Platform data with cost management. After adding the integration, you can view and manage your OpenShift Container Platform and other integrations from the Integrations page in the Hybrid Cloud Console. Prerequisites You are logged in to the Red Hat Hybrid Cloud Console as an Organization Administrator or as a user with Cloud Administrator permissions. You have access to an OpenShift Container Platform environment that you want to use with the Hybrid Cloud Console. Procedure Go to Settings > Integrations . Select the Red Hat tab. Click Add integration to open the integrations wizard. If this is the first integration you are adding, skip this step. Select Red Hat OpenShift Container Platform , and then click . Enter a descriptive name for the integration, for example, my_ocp_integration , and then click . Select Cost Management as the application, and then click . To install and configure the costmanagement-metrics-operator , use the steps in the wizard, and then click . Refer to Integrating OpenShift Container Platform data into cost management for additional information. Enter the Cluster Identifier , and then click . Review the integration details, and then click Add to finish adding the integration. Verification Go to the Integrations page, and select the Red Hat tab. Confirm that your OpenShift Container Platform integration is listed and the status is Ready .

Commands:
Chapter 6. Using your subscription Red Hat Service Interconnect is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. 6.1. Accessing your account Procedure Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. 6.2. Activating a subscription Procedure Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. 6.3. Registering your system for packages To install RPM packages for this product on Red Hat Enterprise Linux, your system must be registered. If you are using downloaded release files, this step is not required. Procedure Go to access.redhat.com . Navigate to Registration Assistant . Select your OS version and continue to the page. Use the listed command in your system terminal to complete the registration. For more information about registering your system, see one of the following resources: Red Hat Enterprise Linux 8 - Registering the system and managing subscriptions Red Hat Enterprise Linux 9 - Registering the system and managing subscriptions

Commands:
Chapter 4. Reviewing inventories with Automation content navigator As a content creator, you can review your Ansible inventory with Automation content navigator and interactively delve into the groups and hosts. 4.1. Reviewing inventory from Automation content navigator You can review Ansible inventories with the Automation content navigator text-based user interface in interactive mode and delve into groups and hosts for more details. Prerequisites A valid inventory file or an inventory plugin. Procedure Start Automation content navigator. USD ansible-navigator Optional: type ansible-navigator inventory -i simple_inventory.yml from the command line to view the inventory. Review the inventory. :inventory -i simple_inventory.yml TITLE DESCRIPTION 0│Browse groups Explore each inventory group and group members members 1│Browse hosts Explore the inventory with a list of all hosts Type 0 to brows the groups. NAME TAXONOMY TYPE 0│general all group 1│nodes all group 2│ungrouped all group The TAXONOMY field details the hierarchy of groups the selected group or node belongs to. Type the number corresponding to the group you want to delve into. NAME TAXONOMY TYPE 0│node-0 all▸nodes host 1│node-1 all▸nodes host 2│node-2 all▸nodes host Type the number corresponding to the host you want to delve into, or type :<number> for numbers greater than 9. [node-1] 0│--- 1│ansible_host: node-1.example.com 2│inventory_hostname: node-1 Verification Review the inventory output. TITLE DESCRIPTION 0│Browse groups Explore each inventory group and group members members 1│Browse hosts Explore the inventory with a list of all hosts Additional resources ansible-inventory . Introduction to Ansible inventories .

Commands:
ansible-navigator
:inventory -i simple_inventory.yml TITLE DESCRIPTION 0│Browse groups Explore each inventory group and group members members 1│Browse hosts Explore the inventory with a list of all hosts
NAME TAXONOMY TYPE 0│general all group 1│nodes all group 2│ungrouped all group
NAME TAXONOMY TYPE 0│node-0 all▸nodes host 1│node-1 all▸nodes host 2│node-2 all▸nodes host
[node-1] 0│--- 1│ansible_host: node-1.example.com 2│inventory_hostname: node-1
TITLE DESCRIPTION 0│Browse groups Explore each inventory group and group members members 1│Browse hosts Explore the inventory with a list of all hosts
Chapter 5. What to do ? Day 2 As a storage administrator, once you have installed and configured Red Hat Ceph Storage 8, you are ready to perform "Day Two" operations for your storage cluster. These operations include adding metadata servers (MDS) and object gateways (RGW), and configuring services such as NFS. For more information about how to use the cephadm orchestrator to perform "Day Two" operations, refer to the Red Hat Ceph Storage 8 Operations Guide . To deploy, configure, and administer the Ceph Object Gateway on "Day Two" operations, refer to the Red Hat Ceph Storage 8 Object Gateway Guide .

Commands:
Chapter 7. Global File System 2 The Red Hat Global File System 2 (GFS2) is a native file system that interfaces directly with the Linux kernel file system interface (VFS layer). When implemented as a cluster file system, GFS2 employs distributed metadata and multiple journals. GFS2 is based on 64-bit architecture, which can theoretically accommodate an 8 exabyte file system. However, the current supported maximum size of a GFS2 file system is 100 TB. If a system requires GFS2 file systems larger than 100 TB, contact your Red Hat service representative. When determining the size of a file system, consider its recovery needs. Running the fsck command on a very large file system can take a long time and consume a large amount of memory. Additionally, in the event of a disk or disk-subsystem failure, recovery time is limited by the speed of backup media. When configured in a Red Hat Cluster Suite, Red Hat GFS2 nodes can be configured and managed with Red Hat Cluster Suite configuration and management tools. Red Hat GFS2 then provides data sharing among GFS2 nodes in a Red Hat cluster, with a single, consistent view of the file system name space across the GFS2 nodes. This allows processes on different nodes to share GFS2 files in the same way that processes on the same node can share files on a local file system, with no discernible difference. For information about the Red Hat Cluster Suite, refer to Red Hat's Cluster Administration guide. A GFS2 must be built on a logical volume (created with LVM) that is a linear or mirrored volume. Logical volumes created with LVM in a Red Hat Cluster suite are managed with CLVM (a cluster-wide implementation of LVM), enabled by the CLVM daemon clvmd , and running in a Red Hat Cluster Suite cluster. The daemon makes it possible to use LVM2 to manage logical volumes across a cluster, allowing all nodes in the cluster to share the logical volumes. For information on the Logical Volume Manager, see Red Hat's Logical Volume Manager Administration guide. The gfs2.ko kernel module implements the GFS2 file system and is loaded on GFS2 cluster nodes. For comprehensive information on the creation and configuration of GFS2 file systems in clustered and non-clustered storage, refer to Red Hat's Global File System 2 guide.

Commands:
Chapter 5. Managing Kickstart and Configuration Files Using authconfig The --update option updates all of the configuration files with the configuration changes. There are a couple of alternative options with slightly different behavior: --kickstart writes the updated configuration to a kickstart file. --test displays the full configuration with changes, but does not edit any configuration files. Additionally, authconfig can be used to back up and restore configurations. All archives are saved to a unique subdirectory in the /var/lib/authconfig/ directory. For example, the --savebackup option gives the backup directory as 2011-07-01 : This backs up all of the authentication configuration files beneath the /var/lib/authconfig/backup-2011-07-01 directory. Any of the saved backups can be used to restore the configuration using the --restorebackup option, giving the name of the manually saved configuration: Additionally, authconfig automatically makes a backup of the configuration before it applies any changes (with the --update option). The configuration can be restored from the most recent automatic backup, without having to specify the exact backup, using the --restorelastbackup option.

Commands:
authconfig --savebackup=2011-07-01
authconfig --restorebackup=2011-07-01
12.2. Managing Object Identifiers Each LDAP object class or attribute must be assigned a unique name and object identifier (OID). An OID is a dot-separated number which identifies the schema element to the server. OIDs can be hierarchical, with a base OID that can be expanded to accommodate different branches. For example, the base OID could be 1 , and there can be a branch for attributes at 1.1 and for object classes at 1.2 . Note It is not required to have a numeric OID for creating custom schema, but Red Hat strongly recommends it for better forward compatibility and performance. OIDs are assigned to an organization through the Internet Assigned Numbers Authority (IANA), and Directory Server does not provide a mechanism to obtain OIDs. To get information about obtaining OIDs, visit the IANA website at http://www.iana.org/cgi-bin/enterprise.pl . After obtaining a base OID from IANA, plan how the OIDs are going to be assigned to custom schema elements. Define a branch for both attributes and object classes; there can also be branches for matching rules and LDAP controls. Once the OID branches are defined, create an OID registry to track OID assignments. An OID registry is a list that gives the OIDs and descriptions of the OIDs used in the directory schema. This ensures that no OID is ever used for more than one purpose. Publish the OID registry with the custom schema.

Commands:
4.2. Installing NFS-Ganesha during an ISO Installation For more information about installing Red Hat Gluster Storage using an ISO image, see Section 2.2, "Installing from an ISO Image" . While installing Red Hat Storage using an ISO, in the Customizing the Software Selection screen, select RH-Gluster-NFS-Ganesha and click . Proceed with the remaining installation steps for installing Red Hat Gluster Storage. For more information on how to install Red Hat Storage using an ISO, see Installing from an ISO Image.

Commands:
Chapter 12. Enabling Chinese, Japanese, or Korean text input If you write with Chinese, Japanese, or Korean characters, you can configure RHEL to input text in your language. 12.1. Input methods Certain scripts, such as Chinese, Japanese, or Korean, require keyboard input to go through an Input Method Engine (IME) to enter native text. An input method is a set of conversion rules between the text input and the selected script. An IME is a software that performs the input conversion specified by the input method. To input text in these scripts, you must set up an IME. If you installed the system in your native language and selected your language at the GNOME Initial Setup screen, the input method for your language is enabled by default. 12.2. Available input method engines The following input method engines (IMEs) are available on RHEL from the listed packages: Table 12.1. Available input method engines Languages Scripts IME name Package Chinese Simplified Chinese Intelligent Pinyin ibus-libpinyin Chinese Traditional Chinese New Zhuyin ibus-libzhuyin Japanese Kanji, Hiragana, Katakana Kana Kanji ibus-kkc Korean Hangul Hangul ibus-hangul Other Various M17N ibus-m17n 12.3. Installing input method engines This procedure installs input method engines (IMEs) that you can use to input Chinese, Japanese, and Korean text. Procedure Install all available input method packages: 12.4. Switching the input method in GNOME This procedure sets up the input method for your script, such as for Chinese, Japanese, or Korean scripts. Prerequisites The input method packages are installed. Procedure Go to the system menu , which is accessible from the top-right screen corner, and click Settings . Select the Region & Language section. In the Input Sources list, review the currently enabled input methods. If your input method is missing: Click the + button under the Input Sources list. Select your language. Note If you cannot find your language in the menu, click the three dots icon ( More... ) at the end of the menu. Select the input method that you want to use. A cog wheel icon marks all input methods to distinguish them from simple keyboard layouts. Confirm your selection by clicking Add . Switch the active input method using one of the following ways: Click the input method indicator on the right side of the top panel and select your input method. Switch between the enabled input methods using the Super + Space keyboard shortcut. Verification Open a text editor. Type text in your language. Verify that the text appears in your native script. 12.5. Additional resources Installing a font for the Chinese standard GB 18030 character set (Red Hat Knowledgebase)

Commands:
yum install @input-methods
10.5. Setting Ethers Information for a Host NIS can host an ethers table which can be used manage DHCP configuration files for systems based on their platform, operating system, DNS domain, and MAC address - all information stored in host entries in IdM. In Identity Management, each system is created with a corresponding ethers entry in the directory, in the ou=ethers subtree. This entry is used to create a NIS map for the ethers service which can be managed by the NIS compatibility plug-in in IdM. To configure NIS maps for ethers entries: Add the MAC address attribute to a host entry. For example: Open the nsswitch.conf file. Add a line for the ethers service, and set it to use LDAP for its lookup. Check that the ethers information is available for the client.

Commands:
cn=server,ou=ethers,dc=example,dc=com
[jsmith@server ~]USD kinit admin [jsmith@server ~]USD ipa host-mod --macaddress=12:34:56:78:9A:BC server.example.com
ethers: ldap
getnt ethers server.example.com