mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 13. Upgrading the Migration Toolkit for Virtualization You can upgrade the MTV Operator by using the Red Hat OpenShift web console to install the new version. Procedure In the Red Hat OpenShift web console, click Operators Installed Operators Migration Toolkit for Virtualization Operator Subscription . Change the update channel to the correct release. See Changing update channel in the Red Hat OpenShift documentation. Confirm that Upgrade status changes from Up to date to Upgrade available . If it does not, restart the CatalogSource pod: Note the catalog source, for example, redhat-operators . From the command line, retrieve the catalog source pod: USD oc get pod -n openshift-marketplace | grep <catalog_source> Delete the pod: USD oc delete pod -n openshift-marketplace <catalog_source_pod> Upgrade status changes from Up to date to Upgrade available . If you set Update approval on the Subscriptions tab to Automatic , the upgrade starts automatically. If you set Update approval on the Subscriptions tab to Manual , approve the upgrade. See Manually approving a pending upgrade in the Red Hat OpenShift documentation. If you are upgrading from MTV 2.2 and have defined VMware source providers, edit the VMware provider by adding a VDDK init image. Otherwise, the update will change the state of any VMware providers to Critical . For more information, see Adding a VMSphere source provider . If you mapped to NFS on the Red Hat OpenShift destination provider in MTV 2.2, edit the AccessModes and VolumeMode parameters in the NFS storage profile. Otherwise, the upgrade will invalidate the NFS mapping. For more information, see Customizing the storage profile .

Commands:
oc get pod -n openshift-marketplace | grep <catalog_source>
oc delete pod -n openshift-marketplace <catalog_source_pod>
2.9. RHEA-2011:0631 - new package: ipa New ipa packages are now available for Red Hat Enterprise Linux 6. Red Hat Enterprise Identity (IPA) is a centralized authentication, identity management and authorization solution for both traditional and cloud based enterprise environments. It integrates components of the Red Hat Directory Server, MIT Kerberos, Red Hat Certificate System, NTP and DNS. It provides web browser and command-line interfaces. Its administration tools allow an administrator to quickly install, set up, and administer a group of IPA servers to meet the authentication and identity management requirements of the large scale Linux and Unix deployments. This enhancement update adds new ipa packages to Red Hat Enterprise Linux 6. (BZ# 658275 ) All users requiring ipa should install these newly-released packages, which add these enhancements.

Commands:
14.5.8. Listing the Link State of a Domain's Virtual Interface This command can be used to query the state of a specified interface on a given domain. Note that if you only want the persistent configuration of the domain to be modified, you need to use the --config option. It should also be noted that for compatibility reasons, --persistent is an alias of --config . The "interface device" can be the interface's target name or the MAC address.

Commands:
domif-getlink rhel6 eth0 up
32.3. Creating the Kickstart File The kickstart file is a simple text file, containing a list of items, each identified by a keyword. You can create it by using the Kickstart Configurator application, or writing it from scratch. The Red Hat Enterprise Linux installation program also creates a sample kickstart file based on the options that you selected during installation. It is written to the file /root/anaconda-ks.cfg . You should be able to edit it with any text editor or word processor that can save files as ASCII text. First, be aware of the following issues when you are creating your kickstart file: Sections must be specified in order . Items within the sections do not have to be in a specific order unless otherwise specified. The section order is: Command section - Refer to Section 32.4, "Kickstart Options" for a list of kickstart options. You must include the required options. The %packages section - Refer to Section 32.5, "Package Selection" for details. The %pre and %post sections - These two sections can be in any order and are not required. Refer to Section 32.6, "Pre-installation Script" and Section 32.7, "Post-installation Script" for details. Note Each section should end with %end to avoid logged warnings. Items that are not required can be omitted. Omitting any required item results in the installation program prompting the user for an answer to the related item, just as the user would be prompted during a typical installation. Once the answer is given, the installation continues unattended (unless it finds another missing item). Lines starting with a pound (also known as hash) sign (#) are treated as comments and are ignored. For kickstart upgrades , the following items are required: Language Installation method Device specification (if device is needed to perform the installation) Keyboard setup The upgrade keyword Boot loader configuration If any other items are specified for an upgrade, those items are ignored (note that this includes package selection).

Commands:
Chapter 1. Overview of alt-java Red Hat packages contain a mitigation for the SSB vulnerability in the form of a patch for the java binary. This patch disables an optimization present in x86-64 (Intel and AMD) processors. Disabling that optimization reduces the risk of kernel side-channel attacks, but also reduces CPU performance. Since the patch reduces performance, it has been removed from the java launcher. A new binary alt-java is now available. From the January 2021 Critical Patch Update release (1.8.0 282.b08, 11.0.10.9) onwards, the alt-java binary is included in Red Hat build of OpenJDK 21 and Red Hat build of OpenJDK 11 GA RPM packages. Additional resources For more information about the performance impact of SSB mitigation, see Kernel Side-Channel Attack using Speculative Store Bypass - CVE-2018-3639 on the Red Hat Customer Portal For more information about the java binary patch, see RH1566890 in the Red Hat Bugzilla documentation.

Commands:
Chapter 2. Architectures Red Hat Enterprise Linux 9.5 is distributed with the kernel version 5.14.0-503.11.1, which provides support for the following architectures at the minimum required version (stated in parentheses): AMD and Intel 64-bit architectures (x86-64-v2) The 64-bit ARM architecture (ARMv8.0-A) IBM Power Systems, Little Endian (POWER9) 64-bit IBM Z (z14) Make sure you purchase the appropriate subscription for each architecture. For more information, see Get Started with Red Hat Enterprise Linux - additional architectures .

Commands:
3.3.4. Option: CPU Pinning Large performance improvements can be obtained by adhering to the system's specific NUMA topology. Use this option to automatically generate a pinning configuration that is valid for the host. Figure 3.7. CPU Pinning Warning Do not use this option if the guest has more vCPUs than a single NUMA node. Using the Pinning option will constrain the guest's vCPU threads to a single NUMA node; however, threads will be able to move around within that NUMA node. For tighter binding capabilities, use the output from the lscpu command to establish a 1:1 physical CPU to vCPU binding using virsh cpupin . Refer to Chapter 9, NUMA for more information on NUMA and CPU pinning.

Commands:
Chapter 4. Installing Red Hat Insights for Red Hat OpenShift Container Platform This chapter provides starting points and resources for registering and installing Red Hat Insights for Red Hat OpenShift Container Platform. You can install, operate, and upgrade your Red Hat OpenShift v4.x clusters from the Red Hat Hybrid Cloud Console. To get started with Red Hat Insights for Red Hat OpenShift Container Platform, you need to confirm that remote health monitoring is still enabled (the default setting) and that cost management is configured. For more information, see: About remote health monitoring Getting started with cost management

Commands:
1.3. Other Red Hat JBoss Data Virtualization Development Red Hat JBoss Data Virtualization is highly extensible in other ways: You can add user defined functions . You can adapt logging to your requirements, which is especially useful for custom audit or command logging. A delegating translator can be used to add custom code to all methods for a given translator. You can also customize authentication and authorization modules. See the Red Hat JBoss Data Virtualization Security Guide .

Commands:
5.9.5. Archiving Files with star The star utility does not retain extended attributes by default. Since SELinux contexts are stored in extended attributes, contexts can be lost when archiving files. Use the star -xattr -H=exustar command to create archives that retain contexts. The star package is not installed by default. To install star , run the yum install star command as the Linux root user. The following example demonstrates creating a Star archive that retains SELinux contexts: As the Linux root user, run the touch /var/www/html/file{1,2,3} command to create three files ( file1 , file2 , and file3 ). These files inherit the httpd_sys_content_t type from the /var/www/html/ directory: Run the cd /var/www/html/ command to change into the /var/www/html/ directory. Once in this directory, as the Linux root user, run the star -xattr -H=exustar -c -f=test.star file{1,2,3} command to create a Star archive named test.star : As the Linux root user, run the mkdir /test command to create a new directory, and then, run the chmod 777 /test/ command to allow all users full-access to the /test/ directory. Run the cp /var/www/html/test.star /test/ command to copy the test.star file in to the /test/ directory. Run the cd /test/ command to change into the /test/ directory. Once in this directory, run the star -x -f=test.star command to extract the Star archive: Run the ls -lZ /test/ command to view the SELinux contexts. The httpd_sys_content_t type has been retained, rather than being changed to default_t , which would have happened had the -xattr -H=exustar option not been used: If the /test/ directory is no longer required, as the Linux root user, run the rm -ri /test/ command to remove it, as well as all files in it. If star is no longer required, as the Linux root user, run the yum remove star command to remove the package. Refer to the star (1) manual page for further information about star .

Commands:
~]# touch /var/www/html/file{1,2,3} ~]# ls -Z /var/www/html/ -rw-r--r-- root root unconfined_u:object_r:httpd_sys_content_t:s0 file1 -rw-r--r-- root root unconfined_u:object_r:httpd_sys_content_t:s0 file2 -rw-r--r-- root root unconfined_u:object_r:httpd_sys_content_t:s0 file3
~]# star -xattr -H=exustar -c -f=test.star file{1,2,3} star: 1 blocks + 0 bytes (total of 10240 bytes = 10.00k).
~]USD star -x -f=test.star star: 1 blocks + 0 bytes (total of 10240 bytes = 10.00k).
~]USD ls -lZ /test/ -rw-r--r-- user1 group1 unconfined_u:object_r:httpd_sys_content_t:s0 file1 -rw-r--r-- user1 group1 unconfined_u:object_r:httpd_sys_content_t:s0 file2 -rw-r--r-- user1 group1 unconfined_u:object_r:httpd_sys_content_t:s0 file3 -rw-r--r-- user1 group1 unconfined_u:object_r:default_t:s0 test.star
6.2. Mounting an Ext4 File System An ext4 file system can be mounted with no extra options. For example: The ext4 file system also supports several mount options to influence behavior. For example, the acl parameter enables access control lists, while the user_xattr parameter enables user extended attributes. To enable both options, use their respective parameters with -o , as in: The tune2fs utility also allows administrators to set default mount options in the file system superblock. For more information on this, refer to man tune2fs . Write Barriers By default, ext4 uses write barriers to ensure file system integrity even when power is lost to a device with write caches enabled. For devices without write caches, or with battery-backed write caches, disable barriers using the nobarrier option, as in: For more information about write barriers, refer to Chapter 22, Write Barriers .

Commands:
mount /dev/ device /mount/point
mount -o acl,user_xattr /dev/ device /mount/point
mount -o nobarrier /dev/ device /mount/point
Appendix A. Using your subscription Streams for Apache Kafka is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Streams for Apache Kafka for Apache Kafka entries in the INTEGRATION AND AUTOMATION category. Select the desired Streams for Apache Kafka product. The Software Downloads page opens. Click the Download link for your component. Installing packages with DNF To install a package and all the package dependencies, use: dnf install <package_name> To install a previously-downloaded package from a local directory, use: dnf install <path_to_download_package> Revised on 2024-05-30 17:23:04 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
7.2. Types The main permission control method used in SELinux targeted policy to provide advanced process isolation is Type Enforcement. All files and processes are labeled with a type: types define a SELinux domain for processes and a SELinux type for files. SELinux policy rules define how types access each other, whether it be a domain accessing a type, or a domain accessing another domain. Access is only allowed if a specific SELinux policy rule exists that allows it. The following types are used with CVS. Different types allow you to configure flexible access: cvs_data_t This type is used for data in a CVS repository. CVS can only gain full access to data if it has this type. cvs_exec_t This type is used for the /usr/bin/cvs binary.

Commands:
4.370. rpcbind 4.370.1. RHBA-2013:1454 - rpcbind bug fix Updated rpcbind packages that fix one bug are now available for Red Hat Enterprise Linux 6. The rpcbind utility maps RPC (Remote Procedure Call) services to the ports on which the services listen and allows the host to make RPC calls to the RPC server. Bug Fix BZ# 858572 Previously, in the insecure mode, which enables non-root users to set or unset ports, a privileged port was required. As only root users can obtain a privileged port, non-root users could not set or unset ports. To fix this bug, the privileged port has been removed, and thus non-root users are now allowed to set or unset ports on the loopback interface. All users of rpcbind are advised to upgrade to these updated packages, which fix this bug.

Commands:
4.246. python-netaddr 4.246.1. RHBA-2011:1658 - python-netaddr bug fix update An updated python-netaddr package that fixes a bug is now available for Red Hat Enterprise Linux 6. The python-netaddr package provides a network address representation and manipulation library for Python. The netaddr library allows Python applications to work with IPv4 and IPv6 addresses, subnetworks, non-aligned IP address ranges and sets, MAC addresses, Organizationally Unique Identifiers (OUI), Individual Address Blocks (IAB), and IEEE EUI-64 identifiers. Bug Fix BZ# 710373 Prior to this update, if an IPNetwork object was instantiated with bad data, the python-netaddr code tried to access an unbound local variable and the erroneous exception "UnboundLocalError" was raised. It should raise the AddrFormatError exception instead. Consequently a user of python-netaddr had to check for all exceptions instead of just "netaddr.core.AddrFormatError". With this update the code is corrected and functions as expected in the scenario described. All users of python-netaddr are advised to upgrade to this updated package, which fixes this bug.

Commands:
3.6. Search: Multiple Criteria and Wildcards Wildcards can be used in the <value> part of the syntax for strings. For example, to find all users beginning with m , enter m* . You can perform a search having two criteria by using the Boolean operators AND and OR . For example: Vms: users.name = m* AND status = Up This query returns all running virtual machines for users whose names begin with "m". Vms: users.name = m* AND tag = "paris-loc" This query returns all virtual machines tagged with "paris-loc" for users whose names begin with "m". When two criteria are specified without AND or OR , AND is implied. AND precedes OR , and OR precedes implied AND .

Commands:
Appendix A. Using your subscription Streams for Apache Kafka is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Streams for Apache Kafka for Apache Kafka entries in the INTEGRATION AND AUTOMATION category. Select the desired Streams for Apache Kafka product. The Software Downloads page opens. Click the Download link for your component. Installing packages with DNF To install a package and all the package dependencies, use: dnf install <package_name> To install a previously-downloaded package from a local directory, use: dnf install <path_to_download_package> Revised on 2025-03-05 17:44:55 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
Chapter 9. Getting started with the pcsd Web UI The pcsd Web UI is a graphical user interface to create and configure Pacemaker/Corosync clusters. 9.1. Setting up the pcsd Web UI Set up your system to use the pcsd Web UI to configure a cluster with the following procedure. Prerequisites The Pacemaker configuration tools are installed. Your system is set up for cluster configuration. For instructions on installing cluster software and setting up your system for cluster configuration, see Installing cluster software . Procedure On any system, open a browser to the following URL, specifying one of the nodes of the cluster (note that this uses the https protocol). This brings up the pcsd Web UI login screen. Log in as user hacluster . This brings up the Clusters page. 9.2. Configuring a high availability pcsd Web UI When you use the pcsd Web UI, you connect to one of the nodes of the cluster to display the cluster management pages. If the node to which you are connecting goes down or becomes unavailable, you can reconnect to the cluster by opening your browser to a URL that specifies a different node of the cluster. It is possible, however, to configure the pcsd Web UI itself for high availability, in which case you can continue to manage the cluster without entering a new URL. Procedure To configure the pcsd Web UI for high availability, perform the following steps. Ensure that the pcsd certificates are synced across the nodes of the cluster by setting PCSD_SSL_CERT_SYNC_ENABLED to true in the /etc/sysconfig/pcsd configuration file. Enabling certificate syncing causes pcsd to sync the certificates for the cluster setup and node add commands. PCSD_SSL_CERT_SYNC_ENABLED is set to false by default. Create an IPaddr2 cluster resource, which is a floating IP address that you will use to connect to the pcsd Web UI. The IP address must not be one already associated with a physical node. If the IPaddr2 resource's NIC device is not specified, the floating IP must reside on the same network as one of the node's statically assigned IP addresses, otherwise the NIC device to assign the floating IP address cannot be properly detected. Create custom SSL certificates for use with pcsd and ensure that they are valid for the addresses of the nodes used to connect to the pcsd Web UI. To create custom SSL certificates, you can use either wildcard certificates or you can use the Subject Alternative Name certificate extension. For information about the Red Hat Certificate System, see the Red Hat Certificate System Administration Guide . Install the custom certificates for pcsd with the pcs pcsd certkey command. Sync the pcsd certificates to all nodes in the cluster with the pcs pcsd sync-certificates command. Connect to the pcsd Web UI using the floating IP address you configured as a cluster resource. Note Even when you configure the pcsd Web UI for high availability, you will be asked to log in again when the node to which you are connecting goes down.

Commands:
https:// nodename :2224
8.5. Additional Resources This section includes various resources that can be used to learn more about disaster recovery and the Red Hat Enterprise Linux-specific subject matter discussed in this chapter. 8.5.1. Installed Documentation The following resources are installed in the course of a typical Red Hat Enterprise Linux installation and can help you learn more about the subject matter discussed in this chapter. tar(1) man page -- Learn how to archive data. dump(8) man page -- Learn how to dump file system contents. restore(8) man page -- Learn how to retrieve file system contents saved by dump . cpio(1) man page -- Learn how to copy files to and from archives. find(1) man page -- Learn how to search for files. amanda(8) man page -- Learn more about the commands that are part of the AMANDA backup system. Files in /usr/share/doc/amanda-server- <version> / -- Learn more about AMANDA by reviewing these various documents and example files.

Commands:
8.48. ftp 8.48.1. RHBA-2013:0845 - ftp bug fix update Updated ftp packages that fix one bug are now available for Red Hat Enterprise Linux 6. The ftp packages provide the standard UNIX command-line File Transfer Protocol (FTP) client. FTP is a widely used protocol for transferring files over the Internet, and for archiving files. Bug Fix BZ# 861113 Prior to this update, when the FTP client was used from a shell with elevated permissions (through the su or the sudo utility), it incorrectly assumed the UID from the original login, instead of the user initiating the client. Consequently, the local home directory was incorrect. With this update, the underlying code has been modified to correctly get the login credentials using the getpwuid(3) utility function call. Now, the local home directory is set according to the user running the client. All users of ftp are advised to upgrade to these updated packages, which fix this bug.

Commands: