mtpti5iD/redhat-docs_dataset huggingface dataset:
17.7. Establishing a Wireless Connection Wireless Ethernet devices are becoming increasingly popular. The configuration is similar to the Ethernet configuration except that it allows you to configure settings such as the SSID and key for the wireless device. To add a wireless Ethernet connection, follow these steps: Click the Devices tab. Click the New button on the toolbar. Select Wireless connection from the Device Type list and click Forward . If you have already added the wireless network interface card to the hardware list, select it from the Wireless card list. Otherwise, select Other Wireless Card to add the hardware device. Note The installation program usually detects supported wireless Ethernet devices and prompts you to configure them. If you configured them during the installation, they are displayed in the hardware list on the Hardware tab. If you selected Other Wireless Card , the Select Ethernet Adapter window appears. Select the manufacturer and model of the Ethernet card and the device. If this is the first Ethernet card for the system, select eth0 ; if this is the second Ethernet card for the system, select eth1 (and so on). The Network Administration Tool also allows the user to configure the resources for the wireless network interface card. Click Forward to continue. On the Configure Wireless Connection page as shown in Figure 17.12, "Wireless Settings" , configure the settings for the wireless device. Figure 17.12. Wireless Settings On the Configure Network Settings page, choose between DHCP and static IP address. You may specify a hostname for the device. If the device receives a dynamic IP address each time the network is started, do not specify a hostname. Click Forward to continue. Click Apply on the Create Wireless Device page. After configuring the wireless device, it appears in the device list as shown in Figure 17.13, "Wireless Device" . Figure 17.13. Wireless Device Be sure to select File => Save to save the changes. After adding the wireless device, you can edit its configuration by selecting the device from the device list and clicking Edit . For example, you can configure the device to activate at boot time. When the device is added, it is not activated immediately, as seen by its Inactive status. To activate the device, select it from the device list, and click the Activate button. If the system is configured to activate the device when the computer starts (the default), this step does not have to be performed again.

Commands:
Chapter 1. Introduction to VDO on LVM The Virtual Data Optimizer (VDO) feature provides inline block-level deduplication, compression, and thin provisioning for storage. You can manage VDO as a type of Logical Volume Manager (LVM) Logical Volumes (LVs), similar to LVM thin-provisioned volumes. VDO volumes on LVM (LVM-VDO) contain the following components: VDO pool LV This is the backing physical device that stores, deduplicates, and compresses data for the VDO LV. The VDO pool LV sets the physical size of the VDO volume, which is the amount of data that VDO can store on the disk. Currently, each VDO pool LV can hold only one VDO LV. As a result, VDO deduplicates and compresses each VDO LV separately. Duplicate data that is stored on separate LVs do not benefit from data optimization of the same VDO volume. VDO LV This is the virtual, provisioned device on top of the VDO pool LV. The VDO LV sets the provisioned, logical size of the VDO volume, which is the amount of data that applications can write to the volume before deduplication and compression occurs. kvdo A kernel module that loads into the Linux Device Mapper layer provides a deduplicated, compressed, and thin provisioned block storage volume. The kvdo module exposes a block device that the VDO pool LV uses to create a VDO LV. The VDO LV is then used by the system. When kvdo receives a request to read a logical block of data from a VDO volume, it maps the requested logical block to the underlying physical block and then reads and returns the requested data. When kvdo receives a request to write a block of data to a VDO volume, it first checks whether the request is a DISCARD or TRIM request or whether the data is uniformly zero. If either of these conditions is met, kvdo updates its block map and acknowledges the request. Otherwise, VDO processes and optimizes the data. The kvdo module utilizes the Universal Deduplication Service (UDS) index on the volume internally and analyzes data, as it is received for duplicates. For each new piece of data, UDS determines if that piece is identical to any previously stored piece of data. If the index finds a match, the storage system can then verify the accuracy of that match and then update internal references to avoid storing the same information more than once. If you are already familiar with the structure of an LVM thin-provisioned implementation, see the following table to understand how the different aspects of VDO are presented to the system. Table 1.1. A comparison of components in VDO on LVM and LVM thin provisioning Physical device Provisioned device VDO on LVM VDO pool LV VDO LV LVM thin provisioning Thin pool Thin volume Since the VDO is thin-provisioned, the file system and applications only see the logical space in use and not the actual available physical space. Use scripting to monitor the available physical space and generate an alert if use exceeds a threshold. For information about monitoring the available VDO space see the Monitoring VDO section.

Commands:
2.6. Devices SR-IOV on the be2net driver, BZ# 602451 The SR-IOV functionality of the Emulex be2net driver is considered a Technology Preview in Red Hat Enterprise Linux 6.3. You must meet the following requirements to use the latest version of SR-IOV support: You must run the latest Emulex firmware (revision 4.1.417.0 or later). The server system BIOS must support the SR-IOV functionality and have virtualization support for Direct I/O VT-d. You must use the GA version of Red Hat Enterprise Linux 6.3. SR-IOV runs on all Emulex-branded and OEM variants of BE3-based hardware, which all require the be2net driver software. Package: kernel-2.6.32-279 iSCSI and FCoE boot iSCSI and FCoE boot support on Broadcom devices is not included in Red Hat Enterprise Linux 6.3. These two features, which are provided by the bnx2i and bnx2fc Broadcom drivers, remain a Technology Preview until further notice. Package: kernel-2.6.32-279 mpt2sas lockless mode The mpt2sas driver is fully supported. However, when used in the lockless mode, the driver is a Technology Preview. Package: kernel-2.6.32-279

Commands:
3.6. Deploy a VDB via AdminShell Prerequisites Red Hat JBoss Data Virtualization must be installed. The JBoss Enterprise Application Platform (EAP) server must be running. Procedure 3.4. Deploy a VDB via AdminShell Open the interactive AdminShell interface Run the ./adminshell.sh command. Open a connection Within the interactive AdminShell, run the connectAsAdmin() command. Deploy your virtual database Run the deploy(" PATH / DATABASE .vdb") command. Close the connection Run the disconnect() command. Exit the interactive shell Enter the exit command to leave the interactive shell. Note In domain mode, when deploying using AdminShell, the VDB is deployed to all available servers. A VDB can also be deployed via the AdminShell console or using a script via the non-interactive AdminShell. For more information on using these, refer to topics on the Administration Shell.

Commands:
Chapter 28. Ref Overview The Ref expression language is really just a way to look up a custom Expression from the Registry . This is particular convenient to use in the XML DSL. The Ref language is part of camel-core . Static import To use the Ref language in your Java application code, include the following import statement in your Java source files: XML example For example, the splitter pattern can reference a custom expression using the Ref language, as follows: Java example The preceding route can also be implemented in the Java DSL, as follows:

Commands:
import static org.apache.camel.language.ref.RefLanguage.ref;
<beans ...> <bean id=" myExpression " class="com.mycompany.MyCustomExpression"/> <camelContext> <route> <from uri="seda:a"/> <split> <ref> myExpression </ref> <to uri="mock:b"/> </split> </route> </camelContext> </beans>
from("seda:a") .split().ref("myExpression") .to("seda:b");
7.47. emacs 7.47.1. RHBA-2015:0238 - emacs bug fix update Updated emacs packages that fix two bugs are now available for Red Hat Enterprise Linux 6. GNU Emacs is a powerful, customizable, self-documenting text editor. It provides special code editing features, a scripting language (elisp), and the capability to read email and news. Bug Fixes BZ# 852516 Previously, the data_space_start value was set inaccurately. As a consequence, the emacs text editor returned the following memory warning message: Emergency (alloc): Warning: past 95% of memory limit To fix this bug, data_space_start has been set correctly, and emacs no longer returns warning messages. BZ# 986989 When using the glyph face encoding, a text face was not removed from the garbage collector. As a consequence, the emacs text editor terminated unexpectedly with a segmentation fault when attempting to remove the face. With this update, the text face is also removed from the garbage collector, and emacs thus no longer crashes in the described scenario. Users of emacs are advised to upgrade to these updated packages, which fix these bugs.

Commands:
4.212. oprofile 4.212.1. RHBA-2011:1712 - oprofile bug fix and enhancement update An updated oprofile package that fixes one bug and adds two enhancements is now available for Red Hat Enterprise Linux 6. OProfile is a system-wide profiler for Linux systems. The profiling runs transparently in the background and profile data can be collected at any time. OProfile uses the hardware performance counters provided on many processors, and can use the Real Time Clock (RTC) for profiling on processors without counters. Bug Fix BZ# 717860 Previously, OProfile could encounter a buffer overrun in the OProfile daemon. This update modifes oprofiled so that OProfile now checks and reports if the filename is too large for the buffer. Enhancements BZ# 696565 Previously, the OProfile profiler did not provide the performance monitoring events for the Intel Sandy Bridge processor. This update provides the files for the Intel Sandy Bridge processor specific performance events and adds the code to identify Intel Sandy Bridge processors. Now, OProfile provides Intel Sandy Bridge specific events. BZ# 695851 Previously, the OProfile profiler did not identify some Intel Westmere processors causing OProfile to use the fallback Intel Architected events. Now, OProfile provides Intel Westmere specific events for Intel Westmere-EX processors (model 0x2f). All OProfile users are advised to upgrade to this updated package which fixes this bug and adds these enhancements.

Commands:
B.42. libnl B.42.1. RHBA-2011:0325 - libnl bug fix update Updated libnl packages that fix a bug are now available for Red Hat Enterprise Linux 6. The libnl package contains a convenience library to simplify using the Linux kernel netlink sockets interface for network manipulation. Bug Fix BZ# 676327 Some nl_send_auto_complete() callers did not free the allocated message when errors were reported, resulting in libnl leaking memory. A problem in its own right, these small leaks also made it more work to detect memory leaks in other processes. With this update, allocated messages are freed correctly when nl_send_auto_complete() is called, and libnl no longer leaks memory in this circumstance. All libnl users should upgrade to these updated packages, which fix this bug.

Commands:
Part I. Choosing a basic or advanced Google Cloud integration To create an Google Cloud integration, first decide if you want to take a basic or advanced integration path. Basic For the basic option, go to Creating a Google Cloud integration: Basic . The basic path enables cost management to directly read your billing reports from GCP at a scope that you indicate. Advanced For the advanced option, go to Creating a Google Cloud integration: Advanced . The advanced path enables you to customize or filter your data before cost management reads it. You might also use the advanced path if you want to share billing data only to certain Red Hat products. The advanced path has more complex setup and configuration. Note You must select either basic or advanced, you cannot choose both.

Commands:
8.158. openslp 8.158.1. RHBA-2014:1482 - openslp bug fix and enhancement update Updated openslp packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. OpenSLP is an open source implementation of the Service Location Protocol (SLP) which is an Internet Engineering Task Force (IETF) standards track protocol and provides a framework to allow networking applications to discover the existence, location, and configuration of networked services in enterprise networks. Note The openslp packages have been upgraded to upstream version 2.0.0, which provides a number of bug fixes and enhancements over the version. (BZ# 1065558 ) Users of openslp are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
4.345. wireshark 4.345.1. RHSA-2012:0509 - Moderate: wireshark security update Updated wireshark packages that fix several security issues are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Wireshark is a program for monitoring network traffic. Wireshark was previously known as Ethereal. Security Fixes CVE-2011-1590 , CVE-2011-4102 , CVE-2012-1595 Several flaws were found in Wireshark. If Wireshark read a malformed packet off a network or opened a malicious dump file, it could crash or, possibly, execute arbitrary code as the user running Wireshark. CVE-2011-1143 , CVE-2011-1957 , CVE-2011-1958 , CVE-2011-1959 , CVE-2011-2174 , CVE-2011-2175 , CVE-2011-2597 , CVE-2011-2698 , CVE-2012-0041 , CVE-2012-0042 , CVE-2012-0067 , CVE-2012-0066 Several denial of service flaws were found in Wireshark. Wireshark could crash or stop responding if it read a malformed packet off a network, or opened a malicious dump file. Users of Wireshark should upgrade to these updated packages, which contain backported patches to correct these issues. All running instances of Wireshark must be restarted for the update to take effect. 4.345.2. RHEA-2011:1772 - wireshark enhancement update An updated wireshark package that provides one enhancement is now available for Red Hat Enterprise Linux 6. Wireshark, previously known as Ethereal, is a network protocol analyzer. It is used to capture and browse the traffic running on a computer network. Enhancement BZ# 746839 Prior to this update, Wireshark did not show traffic information for the Network File System (NFS) version 4.1 protocol. With this update, the NFS packet dissector is enhanced so that Wireshark correctly displays traffic for this protocol. Note that NFS version 4.1 is introduced as a Technology Preview for Red Hat Enterprise Linux 6. Users of wireshark are advised to upgrade to this updated package, which adds this enhancement.

Commands:
11.4.2.3. Specifying a Local Lockfile Lockfiles are very useful with Procmail to ensure that more than one process does not try to alter a message simultaneously. Specify a local lockfile by placing a colon ( : ) after any flags on a recipe's first line. This creates a local lockfile based on the destination file name plus whatever has been set in the LOCKEXT global environment variable. Alternatively, specify the name of the local lockfile to be used with this recipe after the colon.

Commands:
Chapter 24. Updated Drivers Storage Driver Updates The Microsemi Smart Family Controller driver (smartpqi.ko.xz) has been updated to version 1.1.4-115. The HP Smart Array Controller driver (hpsa.ko.xz) has been updated to version 3.4.20-125-RH1. The Emulex LightPulse Fibre Channel SCSI driver (lpfc.ko.xz) has been updated to version 0:12.0.0.5. The Avago MegaRAID SAS driver (megaraid_sas.ko.xz) has been updated to version 07.705.02.00-rh1. The Dell PERC2, 2/Si, 3/Si, 3/Di, Adaptec Advanced Raid Products, HP NetRAID-4M, IBM ServeRAID & ICP SCS driver (aacraid.ko.xz) has been updated to version 1.2.1[50877]-custom. The QLogic FastLinQ 4xxxx iSCSI Module driver (qedi.ko.xz) has been updated to version 8.33.0.20. The QLogic Fibre Channel HBA driver (qla2xxx.ko.xz) has been updated to version 10.00.00.06.07.6-k. The QLogic QEDF 25/40/50/100Gb FCoE driver (qedf.ko.x) has been updated to version 8.33.0.20. The LSI MPT Fusion SAS 3.0 Device driver (mpt3sas.ko.xz) has been updated to version 16.100.01.00. The LSI MPT Fusion SAS 2.0 Device driver (mpt2sas.ko.xz) has been updated to version 20.103.01.00. Network Driver Updates The Realtek RTL8152/RTL8153 Based USB Ethernet Adapters driver (r8152.ko.xz) has been updated to version v1.09.9. The VMware vmxnet3 virtual NIC driver (vmxnet3.ko.xz) has been updated to version 1.4.14.0-k. The Intel(R) Ethernet Connection XL710 Network driver (i40e.ko.xz) has been updated to version 2.3.2-k. The Intel(R) 10 Gigabit Virtual Function Network driver (ixgbevf.ko.xz) has been updated to version 4.1.0-k-rh7.6. The Intel(R) 10 Gigabit PCI Express Network driver (ixgbe.ko.xz) has been updated to version 5.1.0-k-rh7.6. The Intel(R) XL710 X710 Virtual Function Network driver (i40evf.ko.xz) has been updated to version 3.2.2-k. The Intel(R) Ethernet Switch Host Interface driver (fm10k.ko.xz) has been updated to version 0.22.1-k. The Broadcom BCM573xx network driver (bnxt_en.ko.xz) has been updated to version 1.9.1. The Cavium LiquidIO Intelligent Server Adapter driver (liquidio.ko.xz) has been updated to version 1.7.2. The Cavium LiquidIO Intelligent Server Adapter Virtual Function driver (liquidio_vf.ko.xz) has been updated to version 1.7.2. The Elastic Network Adapter (ENA) driver (ena.ko.xz) has been updated to version 1.5.0K. The aQuantia Corporation Network driver (atlantic.ko.xz) has been updated to version 2.0.2.1-kern. The QLogic FastLinQ 4xxxx Ethernet driver (qede.ko.xz) has been updated to version 8.33.0.20. The QLogic FastLinQ 4xxxx Core Module driver (qed.ko.xz) has been updated to version 8.33.0.20. The Cisco VIC Ethernet NIC driver (enic.ko.xz) has been updated to version 2.3.0.53. Graphics Driver and Miscellaneous Driver Updates The VMware Memory Control (Balloon) driver (vmw_balloon.ko.xz) has been updated to version 1.4.1.0-k. The HP watchdog driver (hpwdt.ko.xz) has been updated to version 1.4.0-RH1k. The standalone drm driver for the VMware SVGA device (vmwgfx.ko.xz) has been updated to version 2.14.1.0.

Commands:
Appendix E. Permissions required to provision hosts The following list provides an overview of the permissions a non-admin user requires to provision hosts. Resource name Permissions Additional details Activation Keys view_activation_keys Ansible role view_ansible_roles Required if Ansible is used. Architecture view_architectures Compute profile view_compute_profiles Compute resource view_compute_resources, create_compute_resources, destroy_compute_resources, power_compute_resources Required to provision bare-metal hosts. view_compute_resources_vms, create_compute_resources_vms, destroy_compute_resources_vms, power_compute_resources_vms Required to provision virtual machines. Content Views view_content_views Domain view_domains Environment view_environments Host view_hosts, create_hosts, edit_hosts, destroy_hosts, build_hosts, power_hosts, play_roles_on_host view_discovered_hosts, submit_discovered_hosts, auto_provision_discovered_hosts, provision_discovered_hosts, edit_discovered_hosts, destroy_discovered_hosts Required if the Discovery service is enabled. Hostgroup view_hostgroups, create_hostgroups, edit_hostgroups, play_roles_on_hostgroup Image view_images Lifecycle environment view_lifecycle_environments Location view_locations Medium view_media Operatingsystem view_operatingsystems Organization view_organizations Parameter view_params, create_params, edit_params, destroy_params Product and Repositories view_products Provisioning template view_provisioning_templates Ptable view_ptables Capsule view_smart_proxies, view_smart_proxies_puppetca view_openscap_proxies Required if the OpenSCAP plugin is enabled. Subnet view_subnets Additional resources Creating a Role in Administering Red Hat Satellite Adding Permissions to a Role in Administering Red Hat Satellite Assigning Roles to a User in Administering Red Hat Satellite

Commands:
Chapter 2. Configuring the upgrade strategy for OpenShift AI As a cluster administrator, you can configure either an automatic or manual upgrade strategy for the Red Hat OpenShift AI Operator. Important By default, the Red Hat OpenShift AI Operator follows a sequential update process. This means that if there are several versions between the current version and the version that you intend to upgrade to, Operator Lifecycle Manager (OLM) upgrades the Operator to each of the intermediate versions before it upgrades it to the final, target version. If you configure automatic upgrades, OLM automatically upgrades the Operator to the latest available version, without human intervention. If you configure manual upgrades, a cluster administrator must manually approve each sequential update between the current version and the final, target version. For information about supported versions, see the Red Hat OpenShift AI Life Cycle Knowledgebase article. Prerequisites You have cluster administrator privileges for your OpenShift cluster. The Red Hat OpenShift AI Operator is installed. Procedure Log in to the OpenShift cluster web console as a cluster administrator. In the Administrator perspective, in the left menu, select Operators Installed Operators . Click the Red Hat OpenShift AI Operator. Click the Subscription tab. Under Update approval , click the pencil icon and select one of the following update strategies: Automatic : New updates are installed as soon as they become available. Manual : A cluster administrator must approve any new update before installation begins. Click Save . Additional resources For more information about upgrading Operators that have been installed by using OLM, see Updating installed Operators in OpenShift Dedicated or Updating installed Operators in Red Hat OpenShift Service on AWS (ROSA)

Commands: