mtpti5iD/redhat-docs_dataset huggingface dataset:
3.12. RFKill Many computer systems contain radio transmitters, including Wi-Fi, Bluetooth, and 3G devices. These devices consume power, which is wasted when the device is not in use. RFKill is a subsystem in the Linux kernel that provides an interface through which radio transmitters in a computer system can be queried, activated, and deactivated. When transmitters are deactivated, they can be placed in a state where software can reactive them (a soft block ) or where software cannot reactive them (a hard block ). The RFKill core provides the application programming interface (API) for the subsystem. Kernel drivers that have been designed to support RFkill use this API to register with the kernel, and include methods for enabling and disabling the device. Additionally, the RFKill core provides notifications that user applications can interpret and ways for user applications to query transmitter states. The RFKill interface is located at /dev/rfkill , which contains the current state of all radio transmitters on the system. Each device has its current RFKill state registered in sysfs . Additionally, RFKill issues uevents for each change of state in an RFKill-enabled device. Rfkill is a command-line tool with which you can query and change RFKill-enabled devices on the system. To obtain the tool, install the rfkill package. Use the command rfkill list to obtain a list of devices, each of which has an index number associated with it, starting at 0 . You can use this index number to tell rfkill to block or unblock a device, for example: blocks the first RFKill-enabled device on the system. You can also use rfkill to block certain categories of devices, or all RFKill-enabled devices. For example: blocks all Wi-Fi devices on the system. To block all RFKill-enabled devices, run: To unblock devices, run rfkill unblock instead of rfkill block . To obtain a full list of device categories that rfkill can block, run rfkill help

Commands:
~]# rfkill block 0
~]# rfkill block wifi
~]# rfkill block all
7.163. polkit 7.163.1. RHBA-2015:0692 - polkit bug fix update Updated polkit packages that fix two bugs are now available for Red Hat Enterprise Linux 6. PolicyKit is a toolkit for defining and handling authorizations. It is used for allowing unprivileged processes to speak to privileged processes. Bug Fixes BZ# 1115649 Prior to this update, the polkitd daemon was not restarted after upgrading the polkit package, nor stopped after the package uninstallation. To fix this bug, scriptlets have been added to the polkit package. Upgrading the polkit package to the version shipped in this erratum does not yet restart the polkitd daemon. The daemon will be restarted after future upgrades from this version. BZ# 1130156 Previously, the output of "pkcheck --help" did not match the supported arguments and their expected form. This update removes the unimplemented "--list-temp" option from "pkcheck --help", and fixes other aspects of the text as well. Users of polkit are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 11. Planning for Installation on Power Systems Servers 11.1. Upgrade or Install? While automated in-place upgrades are now supported, the support is currently limited to AMD64 and Intel 64 systems. If you have an existing installation of Red Hat Enterprise Linux on an IBM Power Systems server, you must perform a clean install to migrate to Red Hat Enterprise Linux 7. A clean install is performed by backing up all data from the system, formatting disk partitions, performing an installation of Red Hat Enterprise Linux 7 from installation media, and then restoring any user data.

Commands:
4.106. java-1.5.0-ibm 4.106.1. RHSA-2012:0508 - Critical: java-1.5.0-ibm security update Updated java-1.5.0-ibm packages that fix several security issues are now available for Red Hat Enterprise Linux 5 and 6 Supplementary. The Red Hat Security Response Team has rated this update as having critical 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. The IBM 1.5.0 Java release includes the IBM Java 2 Runtime Environment and the IBM Java 2 Software Development Kit. Security Fixes CVE-2011-3389 , CVE-2011-3557 , CVE-2011-3560 , CVE-2011-3563 , CVE-2012-0498 , CVE-2012-0499 , CVE-2012-0501 , CVE-2012-0502 , CVE-2012-0503 , CVE-2012-0505 , CVE-2012-0506 , CVE-2012-0507 This update fixes several vulnerabilities in the IBM Java 2 Runtime Environment and the IBM Java 2 Software Development Kit. Detailed vulnerability descriptions are linked from the IBM "Security alerts" page. All users of java-1.5.0-ibm are advised to upgrade to these updated packages, containing the IBM 1.5.0 SR13-FP1 Java release. All running instances of IBM Java must be restarted for this update to take effect.

Commands:
Chapter 10. Authentication for Enrolling Certificates This chapter covers how to enroll end entity certificates, how to create and manage server certificates, the authentication methods available in the Certificate System to use when enrolling end entity certificates, and how to set up those authentication methods. Enrollment is the process of issuing certificates to an end entity. The process is creating and submitting the request, authenticating the user requesting it, and then approving the request and issuing the certificate. The method used to authenticate the end entity determines the entire enrollment process. There are three ways that the Certificate System can authenticate an entity: In agent-approved enrollment, end-entity requests are sent to an agent for approval. The agent approves the certificate request. In automatic enrollment, end-entity requests are authenticated using a plug-in, and then the certificate request is processed; an agent is not involved in the enrollment process. In CMC enrollment , a third party application can create a request that is signed by an agent and then automatically processed. A Certificate Manager is initially configured for agent-approved enrollment and for CMC authentication. Automated enrollment is enabled by configuring one of the authentication plug-in modules. More than one authentication method can be configured in a single instance of a subsystem. Note An email can be automatically sent to an end entity when the certificate is issued for any authentication method by configuring automated notifications. See Chapter 12, Using Automated Notifications for more information on notifications. 10.1. Configuring Agent-Approved Enrollment The Certificate Manager is initially configured for agent-approved enrollment. An end entity makes a request which is sent to the agent queue for an agent's approval. An agent can modify request, change the status of the request, reject the request, or approve the request. Once the request is approved, the signed request is sent to the Certificate Manager for processing. The Certificate Manager processes the request and issues the certificate. The agent-approved enrollment method is not configurable. If a Certificate Manager is not configured for any other enrollment method, the server automatically sends all certificate-related requests to a queue where they await agent approval. This ensures that all requests that lack authentication credentials are sent to the request queue for agent approval. To use agent-approved enrollment, leave the authentication method blank in the profile's .cfg file. For example:

Commands:
auth.instance_id=
B.78.2. RHBA-2011:0012 - qemu-kvm bug fix update Updated qemu-kvm packages that fix various bugs are now available for Red Hat Enterprise Linux 6. KVM (Kernel-based Virtual Machine) is a full virtualization solution for Linux on AMD64 and Intel 64 systems. qemu-kvm is the user-space component for running virtual machines using KVM. Bug Fixes BZ# 648821 When running a Windows Server 2008 virtual machine with a virtio network interface controller (NIC), unplugging the NIC could cause qemu-kvm to terminate unexpectedly with a segmentation fault. With this update, the underlying source code has been modified to address this issue, and unplugging such NIC while the virtual machine is active no longer causes qemu-kvm to crash. BZ# 653329 Previously, qemu-kvm did not allow a user to select a resolution higher than 1920x1080, which may have been rather limiting. This update increases the maximum supported resolution to 2560x1600. BZ# 653337 Due to an error in the Russian keyboard layout, pressing the "/" and "|" keys with the "ru" layout enabled produced wrong characters. With this update, the relevant lines in the ru.orig file have been corrected, and pressing these keys now produces the expected results. BZ# 653341 Under certain circumstances, QEMU could stop responding during the installation of an operating system in a virtual machine when the QXL display device was in use. This error no longer occurs, and kvm-qemu now works as expected. BZ# 653343 When running a virtual machine with 4 or more gigabytes of the virtual memory, an attempt to hot plug a network interface controller (NIC) failed with the following error message: Device '[device_name]' could not be initialized This update resolves this issue, and hot-plugging a NIC in a virtual machine with 4 or more gigabytes of the virtual memory no longer fails. BZ# 662058 Previously, the conversion of a disk image by using the "qemu-img convert" command may have been significantly slow. With this update, various patches have been applied to improve the performance of the above command. All users of qemu-kvm are advised to upgrade to these updated packages, which resolve these issues.

Commands:
8.65. hwdata 8.65.1. RHBA-2013:1612 - hwdata bug fix and enhancement update An updated hwdata package that fixes one bug and adds various enhancements is now available for Red Hat Enterprise Linux 6. The hwdata package contains tools for accessing and displaying hardware identification and configuration data. Bug Fix BZ# 989142 Previously, certain information about the Red Hat Virtio Small Computer System Interface (SCSI) device was missing from the pci.ids database. Consequently, when using the lspci utility, the device name was not shown correctly and the numeric device ID was shown instead. With this update, the pci.ids database has been modified to provide correct information as expected. Enhancements BZ# 982659 The PCI ID numbers have been updated for the Beta and the Final compose lists. BZ# 739838 With this update, the pci.ids database has been updated with information about AMD FirePro graphic cards. BZ# 948121 With this update, the pci.ids database has been updated with information about the Cisco VIC SR-IOV Virtual Function with the usNIC capability. All users of hwdata are advised to upgrade to this updated package, which fixes this bug and adds these enhancements.

Commands:
31.3. Loading a Module To load a kernel module, run the modprobe <module_name> command as root. For example, to load the wacom module, run: By default, modprobe attempts to load the module from the /lib/modules/ <kernel_version> /kernel/drivers/ directory. In this directory, each type of module has its own subdirectory, such as net/ and scsi/ , for network and SCSI interface drivers respectively. Some modules have dependencies, which are other kernel modules that must be loaded before the module in question can be loaded. A list of module dependencies is generated and maintained by the depmod program that is run automatically whenever a kernel or driver package is installed on the system. The depmod program keeps the list of dependencies in the /lib/modules/<kernel_version>/modules.dep file. The modprobe command always reads the modules.dep file when performing operations. When you ask modprobe to load a specific kernel module, it first examines the dependencies of that module, if there are any, and loads them if they are not already loaded into the kernel. modprobe resolves dependencies recursively: If necessary, it loads all dependencies of dependencies, and so on, thus ensuring that all dependencies are always met. You can use the -v (or --verbose ) option to cause modprobe to display detailed information about what it is doing, which may include loading module dependencies. The following is an example of loading the Fibre Channel over Ethernet module verbosely: Example 31.3. modprobe -v shows module dependencies as they are loaded This example shows that modprobe loaded the scsi_tgt , scsi_transport_fc , libfc and libfcoe modules as dependencies before finally loading fcoe . Also note that modprobe used the more " primitive " insmod command to insert the modules into the running kernel. Important Although the insmod command can also be used to load kernel modules, it does not resolve dependencies. Because of this, you should always load modules using modprobe instead.

Commands:
~]# modprobe wacom
~]# modprobe -v fcoe insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/scsi_tgt.ko insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/scsi_transport_fc.ko insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/libfc/libfc.ko insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/fcoe/libfcoe.ko insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/fcoe/fcoe.ko
Chapter 5. Changing the CA trust flags The certificate authority (CA) trust flags define for which scenarios Directory Server trusts a CA certificate. For example, you set the flags to trust the certificate for TLS connections to the server and for certificate-based authentication. 5.1. Changing the CA trust flags using the command line You can set the following trust flags on a certificate authority (CA) certificate: C : Trusted CA T : Trusted CA client authentication c : Valid CA P : Trusted peer p : Valid peer u : Private key You specify the trust flags comma-separated in three categories: TLS, email, object signing For example, to trust the CA for TLS encryption and certificate-based authentication, set the trust flags to CT,, . Prerequisites You imported a CA certificate to the network security services (NSS) database. Procedure Use the following command to change the trust flags of a CA certificate: # dsconf -D " cn=Directory Manager " ldap://server.example.com security ca-certificate set-trust-flags " Example CA " --flags " trust_flags " Verification Display all certificates in the NSS database: # certutil -d /etc/dirsrv/slapd- instance_name / -L Certificate Nickname Trust Attributes SSL,S/MIME,JAR/XPI Example CA CT,, Additional resources The certutil(1) man page 5.2. Changing the CA trust flags using the web console You can use the web console to change the CA trust flags. Prerequisites You imported a CA certificate to the network security services (NSS) database. Procedure Navigate to Server Security Certificate Management Trusted Certificate Authorities . Click ... icon to the CA certificate, and select Edit Trust Flags . Select the trust flags. Click Save Verification Navigate to Server Security Certificate Management Trusted Certificate Authorities . Click > to the CA certificate to display the trust flags.

Commands:
dsconf -D " cn=Directory Manager " ldap://server.example.com security ca-certificate set-trust-flags " Example CA " --flags " trust_flags "
certutil -d /etc/dirsrv/slapd- instance_name / -L Certificate Nickname Trust Attributes SSL,S/MIME,JAR/XPI Example CA CT,,
Chapter 2. Installation This chapter guides you through the steps to install AMQ Python in your environment. 2.1. Prerequisites You must have a subscription to access AMQ release files and repositories. To install packages on Red Hat Enterprise Linux, you must register your system . To use AMQ Python, you must install Python in your environment. 2.2. Installing on Red Hat Enterprise Linux Procedure Use the subscription-manager command to subscribe to the required package repositories. If necessary, replace <variant> with the value for your variant of Red Hat Enterprise Linux (for example, server or workstation ). Red Hat Enterprise Linux 6 USD sudo subscription-manager repos --enable=amq-clients-2-for-rhel-6- <variant> -rpms Red Hat Enterprise Linux 7 USD sudo subscription-manager repos --enable=amq-clients-2-for-rhel-7- <variant> -rpms Red Hat Enterprise Linux 8 USD sudo subscription-manager repos --enable=amq-clients-2-for-rhel-8-x86_64-rpms Use the yum command to install the python-qpid-proton and python-qpid-proton-docs packages. USD sudo yum install python-qpid-proton python-qpid-proton-docs For more information about using packages, see Appendix B, Using Red Hat Enterprise Linux packages . 2.3. Installing on Microsoft Windows Procedure Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Red Hat AMQ Clients entry in the INTEGRATION AND AUTOMATION category. Click Red Hat AMQ Clients . The Software Downloads page opens. Download the AMQ Clients 2.8.0 Python .whl file for your Python version. Python 3.6 python_qpid_proton-0.32.0-cp36-cp36m-win_amd64.whl Python 3.8 python_qpid_proton-0.32.0-cp38-cp38-win_amd64.whl Open a command prompt window and use the pip install command to install the .whl file. Python 3.6 > pip install python_qpid_proton-0.32.0-cp36-cp36m-win_amd64.whl Python 3.8 > pip install python_qpid_proton-0.32.0-cp38-cp38-win_amd64.whl

Commands:
sudo subscription-manager repos --enable=amq-clients-2-for-rhel-6- <variant> -rpms
sudo subscription-manager repos --enable=amq-clients-2-for-rhel-7- <variant> -rpms
sudo subscription-manager repos --enable=amq-clients-2-for-rhel-8-x86_64-rpms
sudo yum install python-qpid-proton python-qpid-proton-docs
> pip install python_qpid_proton-0.32.0-cp36-cp36m-win_amd64.whl
> pip install python_qpid_proton-0.32.0-cp38-cp38-win_amd64.whl
14.2.3. Requiring SSH for Remote Connections For SSH to be truly effective, using insecure connection protocols should be prohibited. Otherwise, a user's password may be protected using SSH for one session, only to be captured later while logging in using Telnet. Some services to disable include telnet , rsh , rlogin , and vsftpd . To disable these services, type the following commands at a shell prompt: For more information on runlevels and configuring services in general, see Chapter 12, Services and Daemons .

Commands:
~]# chkconfig telnet off ~]# chkconfig rsh off ~]# chkconfig rlogin off ~]# chkconfig vsftpd off
7.218. tuna 7.218.1. RHBA-2015:1261 - tuna bug fix update An updated tuna package that fixes one bug is now available for Red Hat Enterprise Linux 6. The tuna package provides an interface for changing both scheduler and IRQ tunables at whole-CPU, per-thread, or per-IRQ levels. Tuna allows CPUs to be isolated for use by a specific application and threads and interrupts to be moved to a CPU simply by dragging and dropping them. Bug Fix BZ# 914366 In Red Hat Enterprise 6.5, the oscilloscope utility was generated successfully, but MRG Realtime was unable to install it. With this update, a specific version of tuna is no longer required, and oscilloscope is thus now installed as expected. Users of tuna are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 1. Identity Management Overview The basic identity management concepts for securing applications with various identity stores are covered in the Red Hat JBoss Enterprise Application Platform (JBoss EAP) Security Architecture guide . This guide shows you how to configure various identity stores, such as a filesystem or LDAP, to secure applications. In some cases you can also use certain identity stores, such as LDAP, as an authorization authority. Various role and access information about principals can be stored in an LDAP directory which can then be used directly by JBoss EAP or mapped to existing JBoss EAP roles. Note Using identity stores backed by external datastores, such as databases or LDAP directories, can have a performance impact on authentication and authorization due to the data access and transport between the external datastore and the JBoss EAP instance.

Commands:
Chapter 1. OpenShift Container Platform CLI tools overview A user performs a range of operations while working on OpenShift Container Platform such as the following: Managing clusters Building, deploying, and managing applications Managing deployment processes Developing Operators Creating and maintaining Operator catalogs OpenShift Container Platform offers a set of command-line interface (CLI) tools that simplify these tasks by enabling users to perform various administration and development operations from the terminal. These tools expose simple commands to manage the applications, as well as interact with each component of the system. 1.1. List of CLI tools The following set of CLI tools are available in OpenShift Container Platform: OpenShift CLI (oc) : This is the most commonly used CLI tool by OpenShift Container Platform users. It helps both cluster administrators and developers to perform end-to-end operations across OpenShift Container Platform using the terminal. Unlike the web console, it allows the user to work directly with the project source code using command scripts. Developer CLI (odo) : The odo CLI tool helps developers focus on their main goal of creating and maintaining applications on OpenShift Container Platform by abstracting away complex Kubernetes and OpenShift Container Platform concepts. It helps the developers to write, build, and debug applications on a cluster from the terminal without the need to administer the cluster. Helm CLI : Helm is a package manager for Kubernetes applications which enables defining, installing, and upgrading applications packaged as Helm charts. Helm CLI helps the user deploy applications and services to OpenShift Container Platform clusters using simple commands from the terminal. Knative CLI (kn) : The Knative ( kn ) CLI tool provides simple and intuitive terminal commands that can be used to interact with OpenShift Serverless components, such as Knative Serving and Eventing. Pipelines CLI (tkn) : OpenShift Pipelines is a continuous integration and continuous delivery (CI/CD) solution in OpenShift Container Platform, which internally uses Tekton. The tkn CLI tool provides simple and intuitive commands to interact with OpenShift Pipelines using the terminal. opm CLI : The opm CLI tool helps the Operator developers and cluster administrators to create and maintain the catalogs of Operators from the terminal. Operator SDK : The Operator SDK, a component of the Operator Framework, provides a CLI tool that Operator developers can use to build, test, and deploy an Operator from the terminal. It simplifies the process of building Kubernetes-native applications, which can require deep, application-specific operational knowledge.

Commands: