mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 2. OpenShift Data Foundation upgrade channels and releases In OpenShift Container Platform 4.1, Red Hat introduced the concept of channels for recommending the appropriate release versions for cluster upgrades. By controlling the pace of upgrades, these upgrade channels allow you to choose an upgrade strategy. As OpenShift Data Foundation gets deployed as an operator in OpenShift Container Platform, it follows the same strategy to control the pace of upgrades by shipping the fixes in multiple channels. Upgrade channels are tied to a minor version of OpenShift Data Foundation. For example, OpenShift Data Foundation 4.18 upgrade channels recommend upgrades within 4.18. Upgrades to future releases is not recommended. This strategy ensures that administrators can explicitly decide to upgrade to the minor version of OpenShift Data Foundation. Upgrade channels control only release selection and do not impact the version of the cluster that you install; the odf-operator decides the version of OpenShift Data Foundation to be installed. By default, it always installs the latest OpenShift Data Foundation release maintaining the compatibility with OpenShift Container Platform. So, on OpenShift Container Platform 4.18, OpenShift Data Foundation 4.18 will be the latest version which can be installed. OpenShift Data Foundation upgrades are tied to the OpenShift Container Platform upgrade to ensure that compatibility and interoperability are maintained with the OpenShift Container Platform. For OpenShift Data Foundation 4.18, OpenShift Container Platform 4.18 and 4.18 (when generally available) are supported. OpenShift Container Platform 4.18 is supported to maintain forward compatibility of OpenShift Data Foundation with OpenShift Container Platform. Keep the OpenShift Data Foundation version the same as OpenShift Container Platform in order to get the benefit of all the features and enhancements in that release. Important Due to fundamental Kubernetes design, all OpenShift Container Platform updates between minor versions must be serialized. You must update from OpenShift Container Platform 4.15 to 4.17 and then to 4.18. You cannot update from OpenShift Container Platform 4.17 to 4.18 directly. For more information, see Preparing to perform an EUS-to-EUS update of the Updating clusters guide in OpenShift Container Platform documentation. OpenShift Data Foundation 4.18 offers the following upgrade channel: stable-4.18 stable-4.17 stable-4.18 channel Once a new version is Generally Available, the stable channel corresponding to the minor version gets updated with the new image which can be used to upgrade. You can use the stable-4.18 channel to upgrade from OpenShift Data Foundation 4.17 and upgrades within 4.18. stable-4.17 You can use the stable-4.17 channel to upgrade from OpenShift Data Foundation 4.15 and upgrades within 4.17.

Commands:
7.108. libburn 7.108.1. RHBA-2012:1273 - libburn bug fix update Updated libburn packages that fix one bug are now available for Red Hat Enterprise Linux 6. problem description Libburn is an open-source library for reading, mastering and writing optical discs. For now this means only CD-R and CD-RW. BZ#822906 Prior to this update, libburn library contained the "burn_write_close_track" command, which was redundant and not fully supported by all burning drives. As a consequence, the burning process CD-R or CD-RW could log errors while closing a track after the burning process, even if the data was written correctly. This update removes this redundant call. All users of gfs-kmod are advised to upgrade to these updated packages, which fix this bug.

Commands:
2.4. Unmounting a Hierarchy You can unmount a hierarchy of cgroups with the umount command: For example: If the hierarchy is currently empty (that is, it contains only the root cgroup) the hierarchy is deactivated when it is unmounted. If the hierarchy contains any other cgroups, the hierarchy remains active in the kernel even though it is no longer mounted. To remove a hierarchy, ensure that all child cgroups are removed before you unmount the hierarchy, or use the cgclear command which can deactivate a hierarchy even when it is not empty - refer to Section 2.12, "Unloading Control Groups" .

Commands:
~]# umount /cgroup/ name
~]# umount /cgroup/cpu_and_mem
Chapter 7. Installing an IdM server or replica with custom database settings from an LDIF file You can install an IdM server and IdM replicas with custom settings for the Directory Server database. The following procedure shows you how to create an LDAP Data Interchange Format (LDIF) file with database settings, and how to pass those settings to the IdM server and replica installation commands. Prerequisites You have determined custom Directory Server settings that improve the performance of your IdM environment. See Adjusting IdM Directory Server performance . Procedure Create a text file in LDIF format with your custom database settings. Separate LDAP attribute modifications with a dash (-). This example sets non-default values for the idle timeout and maximum file descriptors. Use the --dirsrv-config-file parameter to pass the LDIF file to the installation script. To install an IdM server: To install an IdM replica: Additional resources Options for the ipa-server-install and ipa-replica-install commands

Commands:
dn: cn=config changetype: modify replace: nsslapd-idletimeout nsslapd-idletimeout: 1800 - replace: nsslapd-maxdescriptors nsslapd-maxdescriptors: 8192
ipa-server-install --dirsrv-config-file filename.ldif
ipa-replica-install --dirsrv-config-file filename.ldif
probe::scsi.set_state Name probe::scsi.set_state - Order SCSI device state change Synopsis Values state_str The new state of the device, as a string dev_id The scsi device id channel The channel number state The new state of the device old_state_str The current state of the device, as a string lun The lun number old_state The current state of the device host_no The host number

Commands:
scsi.set_state
6.2. Confining New Linux Users: useradd Linux users mapped to the SELinux unconfined_u user run in the unconfined_t domain. This is seen by running the id -Z command while logged-in as a Linux user mapped to unconfined_u : When Linux users run in the unconfined_t domain, SELinux policy rules are applied, but policy rules exist that allow Linux users running in the unconfined_t domain almost all access. If unconfined Linux users execute an application that SELinux policy defines can transition from the unconfined_t domain to its own confined domain, unconfined Linux users are still subject to the restrictions of that confined domain. The security benefit of this is that, even though a Linux user is running unconfined, the application remains confined, and therefore, the exploitation of a flaw in the application can be limited by policy. Note This does not protect the system from the user. Instead, the user and the system are being protected from possible damage caused by a flaw in the application. When creating Linux users with the useradd command, use the -Z option to specify which SELinux user they are mapped to. The following example creates a new Linux user, useruuser , and maps that user to the SELinux user_u user. Linux users mapped to the SELinux user_u user run in the user_t domain. In this domain, Linux users are unable to run setuid applications unless SELinux policy permits it (such as passwd ), and cannot run the su or sudo command, preventing them from becoming the Linux root user with these commands. As the Linux root user, run the useradd -Z user_u useruuser command to create a new Linux user ( useruuser ) that is mapped to the SELinux user_u user. As the Linux root user, run the semanage login -l command to view the mapping between the Linux useruuser user and user_u : As the Linux root user, run the passwd useruuser command to assign a password to the Linux useruuser user: Log out of your current session, and log in as the Linux useruuser user. When you log in, pam_selinux maps the Linux user to an SELinux user (in this case, user_u ), and sets up the resulting SELinux context. The Linux user's shell is then launched with this context. Run the id -Z command to view the context of a Linux user: Log out of the Linux useruuser 's session, and log back in with your account. If you do not want the Linux useruuser user, run the userdel -r useruuser command as the Linux root user to remove it, along with its home directory.

Commands:
~]USD id -Z unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
~]# semanage login -l Login Name SELinux User MLS/MCS Range __default__ unconfined_u s0-s0:c0.c1023 root unconfined_u s0-s0:c0.c1023 system_u system_u s0-s0:c0.c1023 useruuser user_u s0
~]# passwd useruuser Changing password for user useruuser. New UNIX password: Enter a password Retype new UNIX password: Enter the same password again passwd: all authentication tokens updated successfully.
~]USD id -Z user_u:user_r:user_t:s0
Chapter 1. Installation overview Red Hat Enterprise Linux AI is distributed and installable as a bootable image. This bootable image includes a container that hold various software and tools for RHEL AI. Each image is compiled to support specific hardware vendors. Each RHEL AI image includes: Red Hat Enterprise Linux 9.4: A RHEL version 9.4 operating system (OS) for your machine. The InstructLab container: Contains InstructLab and various other tools required for RHEL AI. This includes: Python version 3.11: A Python 3.11 installation used internally by InstructLab. The InstructLab tools: The InstructLab command line interface (CLI). The LAB enhanced method of synthetic data generation (SDG). The LAB enhanced method of multi-phase training. InstructLab with vLLM: A high-input inference and serving engine for Large Language models (LLMs). InstructLab with DeepSpeed: A hardware optimization software that speeds up the training process. Similar functionalities of FSDP. InstructLab with FSDP: A training framework that makes training faster and more efficient. Similar functionalities of DeepSpeed Red Hat Enterprise Linux AI version 1.3 also includes a sample taxonomy tree with example skills and knowledge that you can download and use for training a model. For general availability, there are three options for installing and deploying Red Hat Enterprise Linux AI. Installing on bare metal Installing on Amazon Web Service (AWS) Installing on IBM Cloud Installing on Google Cloud Platform (GCP) Installing on Azure After installation with Red Hat Enterprise Linux AI general availability, you can manually download open source Granite LLMs that you can chat and interact with. For more information about downloading these models, see Downloading additional models .

Commands:
12.2.2. Deleting a Storage Pool Using virt-manager This procedure demonstrates how to delete a storage pool. To avoid any issues with other guest virtual machines using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window. Figure 12.6. Stop Icon Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.

Commands:
7.140. numad 7.140.1. RHBA-2015:1441 - numad bug fix update Updated numad packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The numad packages provide a daemon for Non-Uniform Memory Architecture (NUMA) systems, monitors NUMA characteristics, and manages placement of processes and memory to minimize memory latency. The packages also provide an interface that can be used to query the numad daemon for the best manual placement of an application. Bug Fixes BZ# 1150585 Previously, the numad daemon could run out of file descriptors. When upgrading numad on KVM-Hypervisor, the following error messages were returned, after which numad terminated unexpectedly: Could not write 1 to /cgroup/cpuset/libvirt/qemu/vm_name/emulator/cpuset.mems -- errno: 13 The underlying source code has been fixed, and numad no longer crashes in this situation. BZ# 1186724 Prior to this update, superfluous quotes in the numad initscript confused the daemon() function, which subsequently constructed a wrong argument. As a consequence, the following error message was returned: Starting numad: /usr/bin/dirname: extra operand `-i' Try `/usr/bin/dirname --help' for more information. A patch removing the quotes around daemon() parameters fixes this bug, and the error messages are no longer returned. Users of numad are advised to upgrade to these updated packages, which fix these bugs.

Commands:
4.22. blktrace 4.22.1. RHBA-2011:1758 - blktrace bug fix and enhancement update Updated blktrace packages that fix one bug and add one enhancement are now available for Red Hat Enterprise Linux 6. The blktrace packages contain a number of utilities to record the I/O trace information for the kernel to user space, and utilities to analyze and view the trace information. Bug Fix BZ# 705128 Prior to this update, the blkparse code contained a misprint. As a result, blkparse used the wrong variable when printing the PC Writes Completed. This update modifies the code so that blkparse now prints the correct value for PC Writes Completed. Enhancement BZ# 736399 This update adds FLUSH/FUA support to blktrace. All blktrace users are advised to upgrade to these updated packages, which fix this bug and add this enhancement.

Commands:
23.3. Specifying a Configuration File The command-line options and other options, which cannot be set on the command line, can be set in an optional configuration file. No configuration file is read by default, so it needs to be specified at runtime with the -f option. For example: A configuration file equivalent to the -i eth3 -m -S options shown above would look as follows:

Commands:
~]# ptp4l -f /etc/ptp4l.conf
~]# cat /etc/ptp4l.conf [global] verbose 1 time_stamping software [eth3]
Chapter 6. Additional Resources This chapter provides references to other relevant sources of information about Red Hat Software Collections 3.4 and Red Hat Enterprise Linux. 6.1. Red Hat Product Documentation The following documents are directly or indirectly relevant to this book: Red Hat Software Collections 3.4 Packaging Guide - The Packaging Guide for Red Hat Software Collections explains the concept of Software Collections, documents the scl utility, and provides a detailed explanation of how to create a custom Software Collection or extend an existing one. Red Hat Developer Toolset 9.0 Release Notes - The Release Notes for Red Hat Developer Toolset document known problems, possible issues, changes, and other important information about this Software Collection. Red Hat Developer Toolset 9.0 User Guide - The User Guide for Red Hat Developer Toolset contains more information about installing and using this Software Collection. Using Red Hat Software Collections Container Images - This book provides information on how to use container images based on Red Hat Software Collections. The available container images include applications, daemons, databases, as well as the Red Hat Developer Toolset container images. The images can be run on Red Hat Enterprise Linux 7 Server and Red Hat Enterprise Linux Atomic Host. Getting Started with Containers - This guide contains a comprehensive overview of information about building and using container images on Red Hat Enterprise Linux 7 and Red Hat Enterprise Linux Atomic Host. Using and Configuring Red Hat Subscription Manager - The Using and Configuring Red Hat Subscription Manager book provides detailed information on how to register Red Hat Enterprise Linux systems, manage subscriptions, and view notifications for the registered systems. Red Hat Enterprise Linux 6 Deployment Guide - The Deployment Guide for Red Hat Enterprise Linux 6 provides relevant information regarding the deployment, configuration, and administration of this system. Red Hat Enterprise Linux 7 System Administrator's Guide - The System Administrator's Guide for Red Hat Enterprise Linux 7 provides information on deployment, configuration, and administration of this system. 6.2. Red Hat Developers Red Hat Developer Program - The Red Hat Developers community portal. Overview of Red Hat Software Collections on Red Hat Developers - The Red Hat Developers portal provides a number of tutorials to get you started with developing code using different development technologies. This includes the Node.js, Perl, PHP, Python, and Ruby Software Collections. Red Hat Developer Blog - The Red Hat Developer Blog contains up-to-date information, best practices, opinion, product and program announcements as well as pointers to sample code and other resources for those who are designing and developing applications based on Red Hat technologies.

Commands:
Chapter 5. Changes in LLVM Toolset LLVM Toolset has been updated from version 15.0.7 to 16.0.6 on RHEL 8 and RHEL 9. Notable changes include: Improvements to optimization Support for new CPU extensions Improved support for new C++ versions Notable backwards incompatible changes include: Clang's default C++ standard is now gnu++17 instead of gnu++14 . The -Wimplicit-function-declaration , -Wimplicit-int and -Wincompatible-function-pointer-types options now default to error for C code. This might affect the behavior of configure scripts. By default, Clang 16 uses the libstdc++ library version 13 and binutils 2.40 provided by GCC Toolset 13.

Commands:
39.3. File Systems The df command reports the system's disk space usage. If you type the command df at a shell prompt, the output looks similar to the following: By default, this utility shows the partition size in 1 kilobyte blocks and the amount of used and available disk space in kilobytes. To view the information in megabytes and gigabytes, use the command df -h . The -h argument stands for human-readable format. The output looks similar to the following: In the list of mounted partitions, there is an entry for /dev/shm . This entry represents the system's virtual memory file system. The du command displays the estimated amount of space being used by files in a directory. If you type du at a shell prompt, the disk usage for each of the subdirectories is displayed in a list. The grand total for the current directory and subdirectories are also shown as the last line in the list. If you do not want to see the totals for all the subdirectories, use the command du -hs to see only the grand total for the directory in human-readable format. Use the du --help command to see more options. To view the system's partitions and disk space usage in a graphical format, use the Gnome System Monitor by clicking on System => Administration => System Monitor or type gnome-system-monitor at a shell prompt (such as an XTerm). Select the File Systems tab to view the system's partitions. The figure below illustrates the File Systems tab. Figure 39.3. GNOME System Monitor - File Systems

Commands:
Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/VolGroup00-LogVol00 11675568 6272120 4810348 57% / /dev/sda1 100691 9281 86211 10% /boot none 322856 0 322856 0% /dev/shm
Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol00 12G 6.0G 4.6G 57% / /dev/sda1 99M 9.1M 85M 10% /boot none 316M 0 316M 0% /dev/shm
8.192. sblim-cmpi-fsvol 8.192.1. RHBA-2013:1691 - sblim-cmpi-fsvol bug fix update Updated sblim-cmpi-fsvol packages that fix one bug are now available for Red Hat Enterprise Linux 6. The sblim-cmpi-fsvol package provides the filesystem and volume management instrumentation allowing users to obtain information about mounted and unmounted file systems by use of CIM or WBEM technology and infrastructure. Bug Fix BZ# 921482 While enumerating the CIM_UnixLocalFileSystem class instances, certain file systems were shown as disabled although they were mounted. This happened when the entries in the /etc/fstab/ directory used symbolic links or Universally Unique Identifiers (UUIDs). A patch has been provided to fix this bug and the mounted file systems are now displayed correctly. Users of sblim-cmpi-fsvol are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 6. Storage iprutil support for SAS VRAID functions The iprutils package provides utilities to manage and configure SCSI devices that are supported by the ipr SCSI storage device driver. The iprutils package has been updated to support SAS VRAID functions for new 6 GB SAS adapters on IBM POWER7. LVM RAID support In Red Hat Enterprise Linux 6.2, support for MD's RAID personalities has been added to LVM as a Technology Preview . The following basic features are available: create, display, rename, use, and remove RAID logical volumes. Automated fault tolerance is not yet available. It is possible to create RAID logical volumes by specifying the --type <segtype> argument. The following are a few examples: Create a RAID1 array (this is a different implementation of RAID1 than LVM's mirror segment type): Create a RAID5 array (3 stripes + 1 implicit parity): Create a RAID6 array (3 stripes + 2 implicit parity): iSCSI extension for RDMA (iSER) initiator and target iSER initiator and target is now fully supported. Red Hat Enterprise Linux can now function as an iSCSI initiator and storage server in production environments that use InfiniBand and where high throughput and low latency are key requirements. Reduced activation times for LVM devices LVM devices can now be activated or deactivated quicker than before. This is relevant to high-density environments that involve a large number of LVM configurations. An example of this is a host that supports hundreds of virtual guests each using one or more logical volumes. Support for raw ECKD access to the DASD driver Normal I/O operations through the DASD device driver give access only to the data fields of an ECKD device even for track based I/O. In Red Hat Enterprise Linux 6.2, the DASD device driver is extended to give access to whole ECKD tracks including count, key, and data fields.

Commands:
~]# lvcreate --type raid1 -m 1 -L 1G -n my_lv my_vg
~]# lvcreate --type raid5 -i 3 -L 1G -n my_lv my_vg
~]# lvcreate --type raid6 -i 3 -L 1G -n my_lv my_vg