mtpti5iD/redhat-docs_dataset huggingface dataset:
10.2. Creating the RAID Devices and Mount Points Once you have all of your partitions created as software RAID partitions, the following steps create the RAID device and mount point: Select the RAID button on the Disk Druid main partitioning screen (refer to Figure 10.5, "RAID Options" ). Figure 10.5, "RAID Options" appears. Select Create a RAID device . Figure 10.5. RAID Options , Figure 10.6, "Making a RAID Device and Assigning a Mount Point" appears, where you can make a RAID device and assign a mount point. Figure 10.6. Making a RAID Device and Assigning a Mount Point Enter a mount point. Choose the file system type for the partition. At this point you can either configure a dynamic LVM file system or a traditional static ext2/ext3 file system. For more information on configuring LVM on a RAID device, select physical volume (LVM) and then refer to Chapter 8, LVM Configuration . If LVM is not required, continue on with the following instructions. Select a device name such as md0 for the RAID device. Choose your RAID level. You can choose from RAID 0 , RAID 1 , and RAID 5 . If you need assistance in determining which RAID level to implement, refer to Chapter 9, Redundant Array of Independent Disks (RAID) . Note If you are making a RAID partition of /boot/ , you must choose RAID level 1, and it must use one of the first two drives (IDE first, SCSI second). If you are not creating a seperate RAID partition of /boot/ , and you are making a RAID partition for the root file system ( / ), it must be RAID level 1 and must use one of the first two drives (IDE first, SCSI second). Figure 10.7. The /boot/ Mount Error The RAID partitions created appear in the RAID Members list. Select which of these partitions should be used to create the RAID device. If configuring RAID 1 or RAID 5, specify the number of spare partitions. If a software RAID partition fails, the spare is automatically used as a replacement. For each spare you want to specify, you must create an additional software RAID partition (in addition to the partitions for the RAID device). Select the partitions for the RAID device and the partition(s) for the spare(s). After clicking OK , the RAID device appears in the Drive Summary list. Repeat this chapter's entire process for configuring additional partitions, devices, and mount points, such as the root partition ( / ), /home/ , or swap. After completing the entire configuration, the figure as shown in Figure 10.8, "Final Sample RAID Configuration" resembles the default configuration, except for the use of RAID. Figure 10.8. Final Sample RAID Configuration The figure as shown in Figure 10.9, "Final Sample RAID With LVM Configuration" is an example of a RAID and LVM configuration. Figure 10.9. Final Sample RAID With LVM Configuration You can continue with your installation process. Refer to the Installation Guide for further instructions.

Commands:
Appendix B. Revision History Revision History Revision 0.0-0.12 Fri Apr 6 2018 Marek Suchanek Fixed the description of Enhanced SCSI Unit Attention Handling Revision 0.0-0.11 Tue Mar 29 2016 Lenka Spackova Added Keepalived and HAProxy (Clustering). Revision 0.0-0.10 Wed Oct 14 2015 Lenka Spackova Removed Industry Standards and Certification. Revision 0.0-0.9 Thu Mar 26 2015 Milan Navratil Update of the Red Hat Enterprise Linux 6.6 Release Notes - OpenJDK8 fully supported. Revision 0.0-0.7 Tue Aug 26 2014 Milan Navratil Release of the Red Hat Enterprise Linux 6.6 Release Notes.

Commands:
8.146. perl-Makefile-Parser 8.146.1. RHBA-2013:0899 - perl-Makefile-Parser bug fix update An updated perl-Makefile-Parser package that fixes one bug is now available for Red Hat Enterprise Linux 6. The perl-Makefile-Parser initial purpose is to provide basic support for the Makefile::GraphViz module, which is aimed to render the building process specified by a Makefile using the GraphViz library. Bug Fix BZ# 657496 Previously, when the perl-Makefile-Parser source RPM package was built without the perl-Time-HiRes package installed, the building process failed executing the Makefile.PL script. With this update, build-time dependencies on the MDOM::Document::Gmake, MDOM::Util, and Time::HiRes Perl modules have been added to the RPM package and the perl-Makefile-Parser source package can now be built in minimal environment as expected. Users of perl-Makefile-Parser are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 2. Requirements To test this feature, you need an existing Red Hat OpenStack Platform environment with an integrated Ceph back end. See the Deploying an Overcloud with Containerized Red Hat Ceph guide for instructions on how to deploy such an environment. In addition, this scenario assumes that: The Shared File System service will still be installed on the Controller nodes, as is the default behavior; and You intend to only use a single instance of the Ceph File Sysem as the only back end for your Shared File System Service. 2.1. Limitations and Restrictions Given the current state of the involved components, the test scenario in this document has the following limitations and restrictions: Untrusted instance users pose a security risk to the Ceph Storage cluster, as they would have direct access to the public network of the Ceph Storage cluster. Ensure that the cluster you are using is quarantined from the production environment, and that only trusted users have access to the test environment. This release only allows read-write access to shares.

Commands:
14.7. The (Transactional) CarMart Quickstart Using JBoss EAP This CarMart Transactional quickstart requires JBoss Data Grid's Library mode with the JBoss Enterprise Application Platform container. All required libraries (jar files) are bundled with the application and deployed to the server. Caches are configured programmatically and run in the same JVM as the web application. All operations are transactional and are configured at JBossASCacheContainerProvider / TomcatCacheContainerProvider implementation classes for the CacheContainerProvider interface. Report a bug 14.7.1. Quickstart Prerequisites The prerequisites for this quickstart are as follows: Java 6.0 (Java SDK 1.6) or better JBoss Enterprise Application Platform 6.x or JBoss Enterprise Web Server 2.x Maven 3.0 or better Configure the Maven Repository. For details, see Chapter 3, Install and Use the Maven Repositories Report a bug 14.7.2. Build and Deploy the Transactional CarMart Quickstart Prerequisites Ensure that the following prerequisites are met before building and deploying the CarMart quickstart. Configure Maven (See Section 14.7.1, "Quickstart Prerequisites" ) Start JBoss Enterprise Application Platform: In a command line terminal, navigate to the root of the JBoss EAP server directory. Use one of the following commands to start the server with a web profile: For Linux: For Windows: Procedure 14.13. Build and Deploy the Transactional Quickstart Open a command line and navigate to the root directory of this quickstart. Enter the following command to build and deploy the archive: The target/jboss-carmart-tx.war file is deployed to the running instance of the server. Report a bug 14.7.3. View the Transactional CarMart Quickstart The following procedure outlines how to view the CarMart quickstart: Prerequisite The CarMart quickstart must be built and deployed to be viewed. Procedure 14.14. View the CarMart Quickstart To view the application, use your browser to navigate to the following link: Report a bug 14.7.4. Undeploy The Transactional CarMart Quickstart Undeploy the transactional CarMart quickstart as follows: In a command line terminal, navigate to the root directory of the quickstart. Undeploy the archive as follows: Report a bug 14.7.5. Test the Transactional CarMart Quickstart The JBoss Data Grid quickstarts include Arquillian Selenium tests. To run these tests: Stop JBoss EAP, if it is running. In a command line terminal, navigate to root directory for the quickstart. Build the quickstarts as follows: Run the tests as follows: Report a bug

Commands:
USDJBOSS_HOME/bin/standalone.sh
%JBOSS_HOME%\bin\standalone.bat
mvn clean package jboss-as:deploy
http://localhost:8080/jboss-carmart-tx
mvn jboss-as:undeploy
mvn clean package
mvn test -Puitests-jbossas -Das7home=/path/to/server
Chapter 12. steps To start deploying your OpenShift Data Foundation, you can use the internal mode within OpenShift Container Platform or use external mode to make available services from a cluster running outside of OpenShift Container Platform. Depending on your requirement, go to the respective deployment guides. Internal mode Deploying OpenShift Data Foundation using Amazon web services Deploying OpenShift Data Foundation using Bare Metal Deploying OpenShift Data Foundation using VMWare vSphere Deploying OpenShift Data Foundation using Microsoft Azure Deploying OpenShift Data Foundation using Google Cloud [Technology Preview] Deploying OpenShift Data Foundation using Red Hat OpenStack Platform [Technology Preview] Deploying OpenShift Data Foundation using Red Hat Virtualization Platform Deploying OpenShift Data Foundation on IBM Power Deploying OpenShift Data Foundation on IBM Z External mode Deploying OpenShift Data Foundation in external mode

Commands:
Chapter 13. catalog This chapter describes the commands under the catalog command. 13.1. catalog list List services in the service catalog Usage: Table 13.1. Command arguments Value Summary -h, --help Show this help message and exit Table 13.2. Output formatter options Value Summary -f {csv,json,table,value,yaml}, --format {csv,json,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated to show multiple columns --sort-column SORT_COLUMN Specify the column(s) to sort the data (columns specified first have a priority, non-existing columns are ignored), can be repeated --sort-ascending Sort the column(s) in ascending order --sort-descending Sort the column(s) in descending order Table 13.3. CSV formatter options Value Summary --quote {all,minimal,none,nonnumeric} When to include quotes, defaults to nonnumeric Table 13.4. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 13.5. Table formatter options Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show. 13.2. catalog show Display service catalog details Usage: Table 13.6. Positional arguments Value Summary <service> Service to display (type or name) Table 13.7. Command arguments Value Summary -h, --help Show this help message and exit Table 13.8. Output formatter options Value Summary -f {json,shell,table,value,yaml}, --format {json,shell,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated to show multiple columns Table 13.9. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 13.10. Shell formatter options Value Summary --prefix PREFIX Add a prefix to all variable names Table 13.11. Table formatter options Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show.

Commands:
openstack catalog list [-h] [-f {csv,json,table,value,yaml}] [-c COLUMN] [--quote {all,minimal,none,nonnumeric}] [--noindent] [--max-width <integer>] [--fit-width] [--print-empty] [--sort-column SORT_COLUMN] [--sort-ascending | --sort-descending]
openstack catalog show [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty] <service>
9.12. Lightweight Directory Access Protocol (LDAP) Lightweight Directory Access Protocol (LDAP) is a protocol for accessing distributed directory information over over TCP/IP. A directory contains a collection of related data, organized hierarchically in a tree format. Each node in the tree is a directory entry, and each entry consists of a set of attribute-value pairs. Each directory entry has a unique identifier, known as its Distinguished Name (DN). The DN consists of a Relative Distinguished Name (RDN), constructed from an attribute from the entry itself, followed by the parent entry's DN.

Commands:
8.2. openCryptoki The openCryptoki package has been updated to version 3.2. This update includes three main changes. Hardware enablement for the IBM (R) zSeries architecture. Hardware enablement for the IBM (R) Crypto Express4S (CEX4S) adapter. New modes of operation are now supported OFB (Output Feed Back mode) is a digital operation that turns a block cipher into a synchronous stream cipher. CFB (Cipher feedback mode) is an operation that makes a block cipher into a self-synchronizing stream cipher CBC-MAC (Cipher Block Chaining Message Authentication Code) for DES, TDES and AES SHA-2 based HMAC (Hash Message Authentication Code) Ability to sign and verify based on the SHA2 (hash algorithm) with an RSA signature

Commands:
Chapter 1. Availability Red Hat provides a distribution of .NET that enables developers to create applications using the C#, Visual Basic, and F# languages and then deploy them on Red Hat Enterprise Linux (RHEL), Red Hat OpenShift Container Platform, or other platforms. A no-cost Red Hat Enterprise Linux Developer Subscription is available, including a full suite of tools for container development. For RHEL 8.10, RHEL 9.5, and later, .NET 9.0 is available as the following RPMs in the AppStream repositories: Note The AppStream repositories are enabled by default in RHEL 8 and RHEL 9. dotnet-sdk-9.0 : Includes the .NET 9.0 Software Development Kit (SDK) and all the runtimes. dotnet-sdk-aot-9.0 :Includes the Ahead-of-Time(AOT) support for the .NET 9.0 SDK. Install this if you want to AOT-compile your .NET applications. aspnetcore-runtime-9.0 : Includes the .NET runtime and the ASP.NET Core runtime. Install this package to run ASP.NET Core-based applications. dotnet-runtime-9.0 : Includes only the .NET 9.0 runtime. Install this to use the runtime without the SDK. .NET 9.0 is available for aarch64 , ppc64le , s390x , and x86_64 architectures on RHEL 8, RHEL 9, RHEL 10 and OpenShift Container Platform. Full instructions for installing .NET 9.0 on RHEL are available in the Getting started with .NET on RHEL 8 , Getting started with .NET on RHEL 9 guides.

Commands:
7.5. Post-Installation Follow the procedures below: Section 7.7.5.2, "Enabling Signed Audit Logging" Section 14.4.1.1, "TLS Cipher Configuration" Section 14.4.1.3, "Enabling Certificate Revocation Checking for Subsystems" Once you completed the procedures above, follow Section 7.10, "Post-installation Tasks" for additional post-installation actions.

Commands:
Appendix C. Revision History Revision History Revision 0.3-1 Fri Apr 17 2020 Jaroslav Klech Removed the soft_watchdog kernel parameter from chapter 3. Revision 0.3-0 Thu Feb 27 2020 Jaroslav Klech Added a Known Issue note for BZ#1551632 (Kernel). Revision 0.2-9 Mon Oct 07 2019 Jiri Herrmann Clarified a Technology Preview note related to OVMF. Revision 0.2-8 Sun Apr 28 2019 Lenka Spackova Improved wording of a Technology Preview feature description (File Systems). Revision 0.2-7 Mon Feb 04 2019 Lenka Spackova Improved structure of the book. Revision 0.2-6 Tue Apr 17 2018 Lenka Spackova Updated a recommendation related to the sslwrap() deprecation. Revision 0.2-5 Tue Feb 06 2018 Lenka Spackova Added a missing Technology Preview - OVMF (Virtualization). Added information regarding deprecation of containers using the libvirt-lxc tooling. Revision 0.2-4 Mon Oct 30 2017 Lenka Spackova Added information on changes in the ld linker behavior to Deprecated Functionality. Revision 0.2-3 Wed Oct 11 2017 Lenka Spackova Fixed workaround for the megaraid_sas known issue (Kernel). Revision 0.2-2 Wed Sep 13 2017 Lenka Spackova Added information regarding limited support for visuals in the Xorg server. Revision 0.2-1 Fri Jul 14 2017 Lenka Spackova Added kexec to Technology Previews (Kernel). Revision 0.2-0 Fri Jun 23 2017 Lenka Spackova Improved an iostat bug fix description. Revision 0.1-9 Wed May 03 2017 Lenka Spackova A new Pacemaker feature added to Clustering. Revision 0.1-8 Thu Apr 27 2017 Lenka Spackova Red Hat Access Labs renamed to Red Hat Customer Portal Labs. Revision 0.1-7 Thu Mar 30 2017 Lenka Spackova Added a new feature to Storage. Revision 0.1-6 Thu Mar 23 2017 Lenka Spackova Updated the firewalld rebase description (Security). Moved a SELinux-related bug fix description to the correct chapter (Security). Revision 0.1-4 Tue Feb 14 2017 Lenka Spackova Updated the samba rebase description (Authentication and Interoperability). Revision 0.1-2 Fri Jan 20 2017 Lenka Spackova Added a known issue related to bind-dyndb-ldap (Authentication and Interoperability). Revision 0.1-1 Fri Dec 16 2016 Lenka Spackova Runtime Instrumentation for IBM z System has been moved to fully supported features (Hardware Enablement). Added information regarding the default registration URL (System and Subscription Management). Added a note on the WALinuxAgent rebase in the Extras channel (Virtualization). Added a note about a configurable SSH key file for the ABRT reporter-upload tool (Compiler and Tools). Revision 0.1-0 Fri Nov 25 2016 Lenka Spackova Added Intel DIMM management tools to Technology Previews (Hardware Enablement). Added a known issue (Kernel). Revision 0.0-9 Mon Nov 21 2016 Lenka Spackova Updated Known Issues (Authentication and Interoperability, Installation and Booting) and New Features (Compiler and Tools, Kernel, Storage). Revision 0.0-8 Thu Nov 03 2016 Lenka Spackova Release of the Red Hat Enterprise Linux 7.3 Release Notes. Revision 0.0-3 Thu Aug 25 2016 Lenka Spackova Release of the Red Hat Enterprise Linux 7.3 Beta Release Notes.

Commands:
4.3. Installing NFS-Ganesha using yum Execute the following steps to install NFS-Ganesha: The glusterfs-ganesha package can be installed using the following command: NFS-Ganesha is installed along with the above package. nfs-ganesha-gluster and HA packages are also installed. Important Run the following command to install nfs-ganesha-selinux on Red Hat Enterprise Linux 7: Run the following command to install nfs-ganesha-selinux on Red Hat Enterprise Linux 8: Note For instructions on how to configure NFS Ganesha, see NFS Ganesha in Red Hat Gluster Storage 3.5 Administration Guide.

Commands:
yum install glusterfs-ganesha
yum install nfs-ganesha-selinux
dnf install glusterfs-ganesha
4.254. ql2400-firmware 4.254.1. RHBA-2011:1661 - ql2400-firmware bug fix and enhancement update An updated ql2400-firmware package that provides several bug fixes and enhancements is now available for Red Hat Enterprise Linux 6. The ql2400-firmware provides the firmware required to run the QLogic 2400 Series of mass storage adapters. This update upgrades the ql2400 firmware to upstream version 5.06.02, which provides a number of bug fixes and enhancements over the version. (BZ# 730814 ) All users of QLogic 2400 Series Fibre Channel adapters are advised to upgrade to this updated package.

Commands:
17.4.2. The /etc/xinetd.d/ Directory The /etc/xinetd.d/ directory contains the configuration files for each service managed by xinetd and the names of the files correlate to the service. As with xinetd.conf , this directory is read only when the xinetd service is started. For any changes to take effect, the administrator must restart the xinetd service. The format of files in the /etc/xinetd.d/ directory use the same conventions as /etc/xinetd.conf . The primary reason the configuration for each service is stored in a separate file is to make customization easier and less likely to effect other services. To gain an understanding of how these files are structured, consider the /etc/xinetd.d/telnet file: These lines control various aspects of the telnet service: service - Defines the service name, usually one listed in the /etc/services file. flags - Sets any of a number of attributes for the connection. REUSE instructs xinetd to reuse the socket for a Telnet connection. socket_type - Sets the network socket type to stream . wait - Defines whether the service is single-threaded ( yes ) or multi-threaded ( no ). user - Defines what user ID the process runs under. server - Defines the binary executable to be launched. log_on_failure - Defines logging parameters for log_on_failure in addition to those already defined in xinetd.conf . disable - Defines whether the service is active.

Commands:
service telnet { flags = REUSE socket_type = stream wait = no user = root server = /usr/sbin/in.telnetd log_on_failure += USERID disable = yes }
Chapter 1. Configuring the GitOps CLI Important The Red Hat OpenShift GitOps argocd CLI tool is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope . You can configure the GitOps argocd CLI to enable tab completion. 1.1. Enabling tab completion After you install the GitOps argocd CLI, you can enable tab completion to automatically complete argocd commands or suggest options when you press Tab. Note Tab completions only exist for the Bash shell. Prerequisites You must have the GitOps argocd CLI tool installed. You must have bash-completion installed on your local system. Procedure The following procedure enables tab completion for the Bash shell. Save the Bash completion code to a file: USD argocd completion bash > argocd_bash_completion Copy the file to /etc/bash_completion.d/ : USD sudo cp argocd_bash_completion /etc/bash_completion.d/ Alternatively, you can save the file to a local directory and source it from your .bash_profile file instead. Tab completion is enabled when you open a new terminal. 1.2. Additional resources Installing the GitOps CLI Logging in to the Argo CD server in the default mode Basic GitOps argocd commands

Commands:
argocd completion bash > argocd_bash_completion
sudo cp argocd_bash_completion /etc/bash_completion.d/