mtpti5iD/redhat-docs_dataset huggingface dataset:
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 single and 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.2 also includes a sample taxonomy tree with example skills and knowledge that you can download and use for training a model. Current installation options for Red Hat Enterprise Linux AI Installing on bare metal Installing on AWS Installing on IBM Cloud Installing on GCP (technology preview) Installing on Azure (technology preview) 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:
Chapter 4. Setting up IdM Replicas Replicas are essentially clones of existin Identity Management servers, and they share identical core configuration. The replica installation process, then, has two major parts: copying the existing, required server configuration and then installing the replica based on that information. 4.1. Planning the Server/Replica Topologies In the IdM domain, there are three types of machines: Servers, which manage all of the services used by domain members Replicas, which are essentially copies of servers (and, once copied, are identical to servers) Clients, which belong to the Kerberos domains, receive certificates and tickets issued by the servers, and use other centralized services for authentication and authorization A replica is a clone of a specific IdM server. The server and replica share the same internal information about users, machines, certificates, and configured policies. These data are copied from the server to the replica in a process called replication . The two Directory Server instances used by an IdM server - the Directory Server instance used by the IdM server as a data store and the Directory Server instance used by the Dogtag Certificate System to store certificate information - are replicated over to corresponding consumer Directory Server instances used by the IdM replica. The different Directory Server instances recognize each other through replication agreements . An initial replication agreement is created between a master server and replica when the replica is created; additional agreements can be added to other servers or replicas using the ipa-replica-manage command. Figure 4.1. Server and Replica Agreements Once they are installed, replicas are functionally identical to servers. There are some guidelines with multi-master replication which place restrictions on the overall server/replica topology. No more than four replication agreements can be configured on a single server/replica. No more than 20 servers and replicas should be involved in a single Identity Management domain. Every server/replica should have a minimum of two replication agreements to ensure that there are no orphan servers or replicas cut out of the IdM domain if another server fails. One of the most resilient topologies is to create a cell configuration for the servers/replicas, where there are a small number of servers in a cell which all have replication agreements with each other (a tight cell), and then each server has one replication agreement with another server outside the cell, loosely coupling that cell to every other cell in the overall domain. Figure 4.2. Example Topology There are some recommendations on how to accomplish this easily: Have at least one IdM server in each main office, data center, or locality. Preferably, have two IdM servers. Do not have more than four servers per data center. Rather than using a server or replica, small offices can use SSSD to cache credentials and use an off-site IdM server as its data backend.

Commands:
Chapter 1. Red Hat Enterprise Linux 9 This section outlines the packages released for Red Hat Enterprise Linux 9. 1.1. Red Hat Satellite Client 6 for RHEL 9 x86_64 (RPMs) The following table outlines the packages included in the satellite-client-6-for-rhel-9-x86_64-rpms repository. Table 1.1. Red Hat Satellite Client 6 for RHEL 9 x86_64 (RPMs) Name Version Advisory gofer 2.12.5-7.1.el9sat RHBA-2022:96562 katello-agent 3.5.7-3.el9sat RHBA-2022:96562 katello-host-tools 3.5.7-3.el9sat RHBA-2022:96562 katello-host-tools-tracer 3.5.7-3.el9sat RHBA-2022:96562 puppet-agent 7.16.0-2.el9sat RHBA-2022:96562 python3-gofer 2.12.5-7.1.el9sat RHBA-2022:96562 python3-gofer-proton 2.12.5-7.1.el9sat RHBA-2022:96562 python3-qpid-proton 0.35.0-2.el9 RHBA-2022:96562 qpid-proton-c 0.35.0-2.el9 RHBA-2022:96562 rubygem-foreman_scap_client 0.5.0-1.el9sat RHBA-2022:96562 1.2. Red Hat Satellite Client 6 for RHEL 9 ppc64le (RPMs) The following table outlines the packages included in the satellite-client-6-for-rhel-9-ppc64le-rpms repository. Table 1.2. Red Hat Satellite Client 6 for RHEL 9 ppc64le (RPMs) Name Version Advisory gofer 2.12.5-7.1.el9sat RHBA-2022:96562 katello-agent 3.5.7-3.el9sat RHBA-2022:96562 katello-host-tools 3.5.7-3.el9sat RHBA-2022:96562 katello-host-tools-tracer 3.5.7-3.el9sat RHBA-2022:96562 python3-gofer 2.12.5-7.1.el9sat RHBA-2022:96562 python3-gofer-proton 2.12.5-7.1.el9sat RHBA-2022:96562 python3-qpid-proton 0.35.0-2.el9 RHBA-2022:96562 qpid-proton-c 0.35.0-2.el9 RHBA-2022:96562 rubygem-foreman_scap_client 0.5.0-1.el9sat RHBA-2022:96562 1.3. Red Hat Satellite Client 6 for RHEL 9 s390x (RPMs) The following table outlines the packages included in the satellite-client-6-for-rhel-9-s390x-rpms repository. Table 1.3. Red Hat Satellite Client 6 for RHEL 9 s390x (RPMs) Name Version Advisory gofer 2.12.5-7.1.el9sat RHBA-2022:96562 katello-agent 3.5.7-3.el9sat RHBA-2022:96562 katello-host-tools 3.5.7-3.el9sat RHBA-2022:96562 katello-host-tools-tracer 3.5.7-3.el9sat RHBA-2022:96562 python3-gofer 2.12.5-7.1.el9sat RHBA-2022:96562 python3-gofer-proton 2.12.5-7.1.el9sat RHBA-2022:96562 python3-qpid-proton 0.35.0-2.el9 RHBA-2022:96562 qpid-proton-c 0.35.0-2.el9 RHBA-2022:96562 rubygem-foreman_scap_client 0.5.0-1.el9sat RHBA-2022:96562 1.4. Red Hat Satellite Client 6 for RHEL 9 aarch64 (RPMs) The following table outlines the packages included in the satellite-client-6-for-rhel-9-aarch64-rpms repository. Table 1.4. Red Hat Satellite Client 6 for RHEL 9 aarch64 (RPMs) Name Version Advisory gofer 2.12.5-7.1.el9sat RHBA-2022:96562 katello-agent 3.5.7-3.el9sat RHBA-2022:96562 katello-host-tools 3.5.7-3.el9sat RHBA-2022:96562 katello-host-tools-tracer 3.5.7-3.el9sat RHBA-2022:96562 python3-gofer 2.12.5-7.1.el9sat RHBA-2022:96562 python3-gofer-proton 2.12.5-7.1.el9sat RHBA-2022:96562 python3-qpid-proton 0.35.0-2.el9 RHBA-2022:96562 qpid-proton-c 0.35.0-2.el9 RHBA-2022:96562 rubygem-foreman_scap_client 0.5.0-1.el9sat RHBA-2022:96562

Commands:
function::user_int_warn Name function::user_int_warn - Retrieves an int value stored in user space. Synopsis Arguments addr The user space address to retrieve the int from. General Syntax user_ing_warn:long(addr:long) Description Returns the int value from a given user space address. Returns zero when user space and warns (but does not abort) about the failure.

Commands:
function user_int_warn:long(addr:long)
5.3. GFS2 File System Hangs and Requires Reboot of All Nodes If your GFS2 file system hangs and does not return commands run against it, requiring that you reboot all nodes in the cluster before using it, check for the following issues. You may have had a failed fence. GFS2 file systems will freeze to ensure data integrity in the event of a failed fence. Check the messages logs to see if there are any failed fences at the time of the hang. Ensure that fencing is configured correctly. The GFS2 file system may have withdrawn. Check through the messages logs for the word withdraw and check for any messages and calltraces from GFS2 indicating that the file system has been withdrawn. A withdraw is indicative of file system corruption, a storage failure, or a bug. Unmount the file system, update the gfs2-utils package, and execute the fsck command on the file system to return it to service. Open a support ticket with Red Hat Support. Inform them you experienced a GFS2 withdraw and provide sosreports with logs. For information on the GFS2 withdraw function, see Section 4.14, "The GFS2 Withdraw Function" . This error may be indicative of a locking problem or bug. Gather data during one of these occurrences and open a support ticket with Red Hat Support, as described in Section 5.2, "GFS2 File System Hangs and Requires Reboot of One Node" .

Commands:
8.62. freeradius 8.62.1. RHEA-2014:1609 - freeradius enhancement update Updated freeradius packages that add one enhancement are now available for Red Hat Enterprise Linux 6. FreeRADIUS is a high-performance and highly configurable free Remote Authentication Dial In User Service (RADIUS) server, designed to allow centralized authentication and authorization for a network. Enhancement BZ# 1107843 Under certain conditions, the proxy server needs the ability to time out to the home server in less than a second. With this update, three new features addressing this requirement have been added: The home server's "response_window" configuration option now accepts fractional values with down to microsecond precision and the minimum of one millisecond. The "response_window" configuration option with the same precision is now also supported in client sections to enable lowering of the home server's response window for specific clients. The "response_timeouts" configuration option is now supported in home server sections, allowing to specify the number of times when a request is permitted to miss the response window before the home server enters the defunct state. Users of freeradius are advised to upgrade to these updated packages, which add this enhancement.

Commands:
Chapter 27. Storage Driver Updates The hpsa driver has been updated to version 3.4.4-1-RH4. The qla2xxx driver has been updated to version 8.07.00.18.07.2-k. The lpfc driver has been updated to version 10.7.0.1. The megaraid_sas driver has been updated to version 06.807.10.00. The fnic driver has been updated to version 1.6.0.17. The mpt2sas driver has been updated to version 20.100.00.00. The mpt3sas driver has been updated to version 9.100.00.00. The Emulex be2iscsi driver has been updated to version 10.6.0.0r. The aacraid driver has been updated to version 1.2. The bnx2i driver has been updated to version 2.7.10.1. The bnx2fc driver has been updated to version 2.4.2.

Commands:
Chapter 10. Kernel Reservation of memory for crashkernel no longer fails Previously, the reservation of memory for crashkernel in some cases failed with the following error message: This update fixes the step down mechanism so that the upper limit set in the KEXEC_RESERVE_UPPER_LIMIT parameter is not exceeded, which makes the reservation succeed. As a result, the memory reservation for crash kernel now proceeds as expected. (BZ#1349069) The mbind call now allocates memory on the specified NUMA node Previously, using the mbind call for allocation of memory on a Non-Uniform Memory Access (NUMA) node with particular number worked only for the very first invocation. On subsequent calls, the memory was always allocated on NUMA node 0. This update fixes the interaction of the mbind_range() function and the vma_adjust() function. As a result, mbind now allocates memory on the NUMA node with specified number in all cases. (BZ#1277241) The system no longer hangs due to the tasklist_lock variable starvation In a situation with a lot of concurrent processes taking the tasklist_lock variable for reading, the operating system sometimes became unresponsive when it was trying to take tasklist_lock for writing. This update fixes the underlying source code, so that a writer excludes the new readers to prevent the system hang. (BZ#1304864) Intel Xeon v5 no longer causes GPU to hang Previously, on GT3 and GT4 architectures, Intel Xeon v5 integrated graphics could experience problems with GPU lock-up, leading to GPU hang. This bug has been fixed. (BZ#1323945) Kernel no longer panics when loading Intel Xeon v5 integrated graphic cards When loading Intel Xeon v5 integrated graphic cards, a kernel panic sometimes occurred due to a race condition in the kernel firmware loader. This update adds a separate lock that is held throughout the life time of the firmware device, thus protecting the area where the device is registered. As a result, the kernel no longer panics in the described situation. (BZ#1309875) NFS no longer uses FS-Cache when -o fsc is not set Previously, when an NFS share was mounted, FS-Cache was always erroneously enabled even when the -o fsc option was not used in the mount command. Consequently, the cachefilesd service stored files on the NFS share, and other severe problems, such as the kernel becoming unresponsive or terminating unexpectedly, sometimes occurred. With this update, NFS no longer uses FS-Cache if -o fsc is not set. As a result, NFS now uses FS-Cache only when explicitly requested. Note that FS-Cache is provided as a Technology Preview in Red Hat Enterprise Linux 6. (BZ#1353844)

Commands:
Crashkernel reservation failed. Found area can not be reserved: start=0x4000000, size=0x34000000.
4.4. Administrative Controls When administering a home machine, the user must perform some tasks as the root user or by acquiring effective root privileges via a setuid program, such as sudo or su . A setuid program is one that operates with the user ID ( UID ) of the program's owner rather than the user operating the program. Such programs are denoted by a lower case s in the owner section of a long format listing, as in the following example: For the system administrators of an organization, however, choices must be made as to how much administrative access users within the organization should have to their machine. Through a PAM module called pam_console.so , some activities normally reserved only for the root user, such as rebooting and mounting removable media are allowed for the first user that logs in at the physical console (see the chapter titled Pluggable Authentication Modules (PAM) in the Reference Guide for more about the pam_console.so module.) However, other important system administration tasks such as altering network settings, configuring a new mouse, or mounting network devices are not possible without administrative priveleges. As a result, system administrators must decide how much access the users on their network should receive. 4.4.1. Allowing Root Access If the users within an organization are a trusted, computer-savvy group, then allowing them root access may not be an issue. Allowing root access by users means that minor activities, like adding devices or configuring network interfaces, can be handled by the individual users, leaving system administrators free to deal with network security and other important issues. On the other hand, giving root access to individual users can lead to the following issues: Machine Misconfiguration - Users with root access can misconfigure their machines and require assistance or worse, open up security holes without knowing it. Running Insecure Services - Users with root access may run insecure servers on their machine, such as FTP or Telnet, potentially putting usernames and passwords at risk as they pass over the network in the clear. Running Email Attachments As Root - Although rare, email viruses that affect Linux do exist. The only time they are a threat, however, is when they are run by the root user.

Commands:
-rwsr-xr-x 1 root root 47324 May 1 08:09 /bin/su
5.2.4. Creating the File System The following command creates a GFS file system on the logical volume. The following commands mount the logical volume and report the file system disk space usage.

Commands:
gfs_mkfs -plock_nolock -j 1 /dev/striped_vol_group/striped_logical_volume This will destroy any data on /dev/striped_vol_group/striped_logical_volume. Are you sure you want to proceed? [y/n] y Device: /dev/striped_vol_group/striped_logical_volume Blocksize: 4096 Filesystem Size: 492484 Journals: 1 Resource Groups: 8 Locking Protocol: lock_nolock Lock Table: Syncing All Done
mount /dev/striped_vol_group/striped_logical_volume /mnt df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/VolGroup00-LogVol00 13902624 1656776 11528232 13% / /dev/hda1 101086 10787 85080 12% /boot tmpfs 127880 0 127880 0% /dev/shm /dev/striped_vol_group/striped_logical_volume 1969936 20 1969916 1% /mnt
Chapter 15. Browsing files on a network share You can connect to a network share provided by a server and browse the files on the server like local files. You can download or upload files using the file browser. 15.1. GVFS URI format for network shares GNOME uses the GVFS URI format to refer to network shares and files on them. When you connect to a network share from GNOME, you provide the address to the network share in the following format. A URL, or uniform resource locator, is a form of address that refers to a location or file on a network. The address is formatted like this: The basic GVFS URI format takes the following syntax: The scheme specifies the protocol or type of server. The example.com portion of the address is called the domain name. If a username is required, it is inserted before the server name: You can also specify the user name or the port number to the network share: Table 15.1. Common network share protocols Protocol GVFS URI example SSH ssh://user@server.example.com/path NFS nfs://server/path Windows SMB smb://server/Share WebDAV dav://example.server.com/path Public FTP ftp://ftp.example.com/path Authenticated FTP ftp://user@ftp.example.com/path Additional resources The GVFS system The format of the GVFS URI string 15.2. Mounting a storage volume in GNOME You can manually mount a local storage volume or a network share in the Files application. Procedure Open the Files application. Click Other Locations in the side bar. The window lists all connected storage volumes and all network shares that are publicly available on your local area network. If you can see the volume or network share in this list, mount it by clicking the item. If you want to connect to a different network share, use the following steps. Enter the GVFS URI string to the network share in the Connect to Server field. Press Connect . If the dialog asks you for login credentials, enter your name and password into the relevant fields. When the mounting process finishes, you can browse the files on the volume or network share. 15.3. Unmounting a storage volume in GNOME You can unmount a storage volume, a network share, or another resource in the Files application. Procedure Open the Files application. In the side bar, click the Unmount (⏏) icon to the chosen mount. Wait until the mount disappears from the side bar or a notification about the safe removal appears. 15.4. Additional resources Managing storage volumes in GNOME Mounting NFS shares Mounting an SMB Share on Red Hat Enterprise Linux

Commands:
protocol :// server.example.com / folder/file
protocol :// user @ server.example.com : port / folder/file
3.9. Creating a Virtual Machine This Ruby example creates a virtual machine. This example uses a hash with symbols and nested hashes as their values. Another method, more verbose, is to use the constructors of the corresponding objects directly. See Creating a Virtual Machine Instance with Attributes for more information. # Get the reference to the "vms" service: vms_service = connection.system_service.vms_service # Use the "add" method to create a new virtual machine: vms_service.add( OvirtSDK4::Vm.new( name: 'myvm', cluster: { name: 'mycluster' }, template: { name: 'Blank' } ) ) After creating a virtual machine, it is recommended to poll the virtual machine's status , to ensure that all the disks have been created. For more information, see http://www.rubydoc.info/gems/ovirt-engine-sdk/OvirtSDK4/VmsService:add .

Commands:
Get the reference to the "vms" service: vms_service = connection.system_service.vms_service Use the "add" method to create a new virtual machine: vms_service.add( OvirtSDK4::Vm.new( name: 'myvm', cluster: { name: 'mycluster' }, template: { name: 'Blank' } ) )
7.142. openhpi32 7.142.1. RHBA-2015:1449 - openhpi32 bug fix and enhancement update Updated openhpi32 packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. OpenHPI is an open source project created with the intent of providing an implementation of the SA Forum's Hardware Platform Interface (HPI). HPI provides an abstracted interface to managing computer hardware, typically for chassis and rack based servers. HPI includes resource modeling; access to and control over sensor, control, watchdog, and inventory data associated with resources; abstracted System Event Log interfaces; hardware events and alerts; and a managed hot swap interface. Note The openhpi32 packages have been upgraded to upstream version 3.4.0, which provides a number of bug fixes and enhancements over the version. (BZ# 1127907 ) Bug Fixes BZ# 1127907 Encryption of the configuration file is now allowed, so authentication credentials for hardware management are no longer available in clear text on the system. Support for IPv6 has been fixed in the Onboard Administrator (OA) SOAP plug-in. The uid_map file is no longer created as world-writable. BZ# 1069015 Prior to this update, a data race condition was present in the Intelligent Platform Management Interface (IPMI) plug-in within the multi-threaded daemon. Consequently, the openhpid daemon could terminate unexpectedly with a segmentation fault. This bug has been fixed, the data structures are now updated in the correct order, and openhpid no longer crashes in this scenario. BZ# 1105679 Network timeouts were handled incorrectly in the openhpid daemon. As a consequence, network connections could fail when external plug-ins were used. With this update, handling of network socket timeouts has been improved in openhpid, and the described problem no longer occurs. Users of openhpi32 are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands: