mtpti5iD/redhat-docs_dataset huggingface dataset:
B.90. subversion B.90.1. RHSA-2011:0258 - Moderate: subversion security update Updated subversion packages that fix three 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 scores, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Subversion (SVN) is a concurrent version control system which enables one or more users to collaborate in developing and maintaining a hierarchy of files and directories while keeping a history of all changes. The mod_dav_svn module is used with the Apache HTTP Server to allow access to Subversion repositories via HTTP. CVE-2010-3315 An access restriction bypass flaw was found in the mod_dav_svn module. If the SVNPathAuthz directive was set to "short_circuit", certain access rules were not enforced, possibly allowing sensitive repository data to be leaked to remote users. Note that SVNPathAuthz is set to "On" by default. CVE-2010-4644 A server-side memory leak was found in the Subversion server. If a malicious, remote user performed "svn blame" or "svn log" operations on certain repository files, it could cause the Subversion server to consume a large amount of system memory. CVE-2010-4539 A NULL pointer dereference flaw was found in the way the mod_dav_svn module processed certain requests. If a malicious, remote user issued a certain type of request to display a collection of Subversion repositories on a host that has the SVNListParentPath directive enabled, it could cause the httpd process serving the request to crash. Note that SVNListParentPath is not enabled by default. All Subversion users should upgrade to these updated packages, which contain backported patches to correct these issues. After installing the updated packages, the Subversion server must be restarted for the update to take effect: restart httpd if you are using mod_dav_svn, or restart svnserve if it is used.

Commands:
Chapter 29. Uninstalling the integrated IdM DNS service from an IdM server If you have more than one server with integrated DNS in an Identity Management (IdM) deployment, you might decide to remove the integrated DNS service from one of the servers. To do this, you must first decommission the IdM server completely before re-installing IdM on it, this time without the integrated DNS. Note While you can add the DNS role to an IdM server, IdM does not provide a method to remove only the DNS role from an IdM server: the ipa-dns-install command does not have an --uninstall option. Prerequisites You have integrated DNS installed on an IdM server. This is not the last integrated DNS service in your IdM topology. Procedure Identify the redundant DNS service and follow the procedure in Uninstalling an IdM server on the IdM replica that hosts this service. On the same host, follow the procedure in either Without integrated DNS, with an integrated CA as the root CA or Without integrated DNS, with an external CA as the root CA , depending on your use case.

Commands:
14.12.6. Uploading and Downloading Storage Volumes This section will instruct how to upload and download information to and from storage volumes. 14.12.6.1. Uploading contents to a storage volume The vol-upload --pool pool-or-uuid --offset bytes --length bytes vol-name-or-key-or-path local-file command uploads the contents of specified local-file to a storage volume. The command requires --pool pool-or-uuid which is the name or UUID of the storage pool the volume is in. It also requires vol-name-or-key-or-path which is the name or key or path of the volume to wipe. The --offset option is the position in the storage volume at which to start writing the data. --length length dictates an upper limit for the amount of data to be uploaded. An error will occur if the local-file is greater than the specified --length .

Commands:
Chapter 2. Enabling applications that are connected to OpenShift AI You must enable SaaS-based applications before using them with Red Hat OpenShift AI. On-cluster applications are enabled automatically. Typically, you can install, or enable applications connected to OpenShift AI using one of the following methods: Enabling the application from the Explore page on the OpenShift AI dashboard, as documented in the following procedure. Installing the Operator for the application from OperatorHub. OperatorHub is a web console for cluster administrators to discover and select Operators to install on their cluster. It is deployed by default in OpenShift ( Installing from OperatorHub using the web console ). Note Deployments containing Operators installed from OperatorHub may not be fully supported by Red Hat. Installing the Operator for the application from Red Hat Marketplace ( Install Operators ). Installing the application as an Add-on to your OpenShift Dedicated ( Adding Operators to an OpenShift Dedicated cluster ) or ROSA cluster ( Adding Operators to a ROSA cluster ). For some applications (such as Jupyter), the API endpoint is available on the tile for the application on the Enabled page of OpenShift AI. Certain applications cannot be accessed directly from their tiles, for example, OpenVINO provides notebook images for use in Jupyter and does not provide an endpoint link from its tile. Additionally, it may be useful to store these endpoint URLs as environment variables for easy reference in a notebook environment. Some independent software vendor (ISV) applications must be installed in specific namespaces. In these cases, the tile for the application in the OpenShift AI dashboard specifies the required namespace. To help you get started quickly, you can access the application's learning resources and documentation on the Resources page, or on the Enabled page by clicking the relevant link on the tile for the application. Prerequisites You have logged in to Red Hat OpenShift AI. Your administrator has installed or configured the application on your OpenShift cluster. Procedure On the OpenShift AI home page, click Explore . On the Explore page, find the tile for the application that you want to enable. Click Enable on the application tile. If prompted, enter the application's service key and then click Connect . Click Enable to confirm that you want to enable the application. Verification The application that you enabled appears on the Enabled page. The API endpoint is displayed on the tile for the application on the Enabled page.

Commands:
37.3. Additional Resources For more information on kernel modules and their utilities, refer to the following resources. 37.3.1. Installed Documentation lsmod man page - description and explanation of its output. insmod man page - description and list of command line options. modprobe man page - description and list of command line options. rmmod man page - description and list of command line options. modinfo man page - description and list of command line options. /usr/share/doc/kernel-doc- <version> /Documentation/kbuild/modules.txt - how to compile and use kernel modules.

Commands:
3.14. Software Collection Kernel Module Support Because Linux kernel modules are normally tied to a particular version of the Linux kernel, you must be careful when you package kernel modules into a Software Collection. This is because the package management system on Red Hat Enterprise Linux does not automatically update or install an updated version of the kernel module if an updated version of the Linux kernel is installed. To make packaging the kernel modules into the Software Collection easier, see the following recommendations. Ensure that: the name of your kernel module package includes the kernel version, the tag Requires , which can be found in your kernel module spec file, includes the kernel version and revision (in the format kernel- version - revision ).

Commands:
Chapter 3. Troubleshooting issues related to SELinux For diagnosing issues related to SELinux, you can check the file /var/log/audit/audit.log , as follows: To query Audit logs, use the ausearch tool. SELinux decisions, such as allowing or disallowing access, are cached in the Access Vector Cache (AVC). Therefore, you should use the AVC and USER_AVC values for the message type parameter, for example: If there are no matches, check if the Audit daemon is running. If it is not running, then perform the following steps: Restart the audit. Re-run the denied scenario. Check the Audit log again. For more information about solving SELinux related issues, see Troubleshooting problems related to SELinux .

Commands:
ausearch -m AVC,USER_AVC,SELINUX_ERR,USER_SELINUX_ERR -ts boot
Part II. Technology Previews This chapter provides a list of all Technology Previews available in Red Hat Enterprise Linux 6.10. Technology Preview features are currently not supported under Red Hat Enterprise Linux subscription services, may not be functionally complete, and are generally not suitable for production use. However, these features are included as a customer convenience and to provide the feature with wider exposure. Customers may find these features useful in a non-production environment. Customers are also free to provide feedback and functionality suggestions for a Technology Preview feature before it becomes fully supported. Errata will be provided for high-severity security issues. During the development of a Technology Preview feature, additional components may become available to the public for testing. It is the intention of Red Hat clustering to fully support Technology Preview features in a future release. For information on Red Hat scope of support for Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/ .

Commands:
Chapter 2. Installing Image Builder Before using Image Builder, you must install Image Builder in a virtual machine. 2.1. Installing Image Builder in a virtual machine To install Image Builder on a dedicated virtual machine, follow these steps: Prerequisites Connect to the virtual machine. The virtual machine for Image Builder must be installed, subscribed, and running. Procedure 1. Install the Image Builder and other necessary packages on the virtual machine: lorax-composer composer-cli cockpit-composer bash-completion 2. Enable Image Builder to start after each reboot: The lorax-composer and cockpit services start automatically on first access. 3. Configure the system firewall to allow access to the web console: 4. Load the shell configuration script so that the auto-complete feature for the composer-cli tool starts working immediately without reboot:

Commands:
yum install lorax-composer composer-cli cockpit-composer bash-completion
systemctl enable lorax-composer.socket
systemctl enable cockpit.socket
firewall-cmd --add-service=cockpit && firewall-cmd --add-service=cockpit --permanent
source /etc/bash_completion.d/composer-cli
Chapter 9. Authentication and Interoperability Identity Management Red Hat Enterprise Linux 6.2 includes identity management capabilities that allow for central management of user identities, policy-based access control and authentication services. This identity management service, previously referred to as IPA, is based on the open source FreeIPA project. These services have been present as a Technology Preview in Red Hat Enterprise Linux 6 releases. With this release, identity management has been promoted to fully supported. Note The Identity Management Guide provides detailed information about the Identity Management solution, the technologies with which it works, and some of the terminology used to describe it. It also provides high-level design information for both the client and server components. PIV support for smart cards Support for smart cards with a PIV (Personal Identity Verification) interface has been added in Red Hat Enterprise Linux 6.2. It is now possible to use FIPS 201 compliant PIV cards that allow for secure use of data. PIV cards enable confidentiality of data by restricting access to the card holder. They also ensure data integrity by allowing only the card holder to make modifications. They guarantee the authenticity of the information and prevent non-repudiation of data. The use of PIV cards is mandated by the U.S. Homeland Security Presidential Directive 12 (HSPC-12) which requires the use of this type of technology to gain access to all government IT systems.

Commands:
2.2.2. Kickstart This section describes what behaviors have changed in automated installations (Kickstart). 2.2.2.1. Behavioral Changes Previously, a Kickstart file that did not have a network line resulted in the assumption that DHCP is used to configure the network. This was inconsistent with the rest of Kickstart in that all other missing lines mean installation will halt and prompt for input. Now, having no network line means that installation will halt and prompt for input if network access is required. If you want to continue using DHCP without interruption, add network --bootproto=dhcp to your Kickstart file. Also, the --bootproto=query option is deprecated. If you want to prompt for network configuration in the first stage of installation, use the asknetwork option. In versions of Red Hat Enterprise Linux, the -server DHCP option was used to specify an NFS server containing Kickstart files when the ks option is passed to the system without a value. This DHCP option has changed to server-name in Red Hat Enterprise Linux 6. Traditionally, disks have been referred to throughout Kickstart by a device node name (such as sda ). The Linux kernel has moved to a more dynamic method where device names are not guaranteed to be consistent across reboots, so this can complicate usage in Kickstart scripts. To accommodate stable device naming, you can use any item from /dev/disk in place of a device node name. For example, instead of: You could use an entry similar to one of the following: This provides a consistent way to refer to disks that is more meaningful than just sda . This is especially useful in large storage environments. You can also use shell-like entries to refer to multiple disks. This is primarily intended to make it easier to use the clearpart and ignoredisk commands in large storage environments. For example, instead of: You could use an entry similar to the following: Kickstart will halt with an error in more cases than versions. For example, if you refer to a disk that does not exist, the installation will halt and inform you of the error. This is designed to help detect errors in Kickstart files before they lead to larger problems. As a side-effect, files that are designed to be generic across different machine configurations can fail more frequently. These must be dealt with on a case-by-case basis. The /tmp/netinfo file used for Kickstart network information has been removed. Anaconda now uses NetworkManager for interface configuration by default, and stores configuration in the ifcfg files in /etc/sysconfig/network-scripts/ . It is possible to use this new location as a source of network settings for %pre and %post scripts.

Commands:
part / --fstype=ext4 --onpart=sda1
part / --fstype=ext4 --onpart=/dev/disk/by-path/pci-0000:00:05.0-scsi-0:0:0:0-part1 part / --fstype=ext4 --onpart=/dev/disk/by-id/ata-ST3160815AS_6RA0C882-part1
ignoredisk --drives=sdaa,sdab,sdac
ignoredisk --drives=/dev/disk/by-path/pci-0000:00:05.0-scsi-*
9. Clustering Clusters are multiple computers (nodes) working in concert to increase reliability, scalability, and availability to critical production services. High Availability using Red Hat Enterprise Linux 6 can be deployed in a variety of configurations to suit varying needs for performance, high-availability, load balancing, and file sharing. The following major updates to clustering are available in Red Hat Enterprise Linux 6.1 Rgmanager now supports the concept of critical and non-critical resources System Administrators can now configure and run a cluster using command line tools. This feature provides an alternative to manually editing the cluster.conf configuration file or using the graphical configuration tool, Luci. Red Hat Enterprise Linux High Availability on Red Hat Enterprise Linux KVM hosts is fully supported Comprehensive SNMP Trap support from central cluster daemons and sub-parts Additional watchdog integration allows a node to reboot itself when it loses quorum The development library packages provided in the High Availability, Load Balancer, and Resilient Storage Add-On channels are not considered supported nor are their ABIs or APIs guaranteed to be consistent. Note The Cluster Administration document describes the configuration and management of Red Hat cluster systems for Red Hat Enterprise Linux 6.

Commands:
B.110. yum B.110.1. RHBA-2010:0846 - yum bug fix update An updated yum package that fixes various bugs is now available. Yum is a utility that can check for and automatically download and install updated RPM packages. Dependencies are obtained and downloaded automatically, prompting the user for permission as necessary. Bug Fixes BZ# 634974 Previously, yum treated packages that provide kernel-modules as install-only packages. With this update, the install-only option has been removed. BZ# 637086 Previously, the "/var/cache/yum/" directory kept accumulating multiple '.sqlite' files and never cleaned them out. With this update, the '.sqlite' are automatically cleaned up. All users of yum are advised to upgrade to this updated package, which resolves these issues.

Commands:
Appendix A. Applying custom configuration to Red Hat Satellite When you install and configure Satellite for the first time using satellite-installer , you can specify that the DNS and DHCP configuration files are not to be managed by Puppet using the installer flags --foreman-proxy-dns-managed=false and --foreman-proxy-dhcp-managed=false . If these flags are not specified during the initial installer run, rerunning of the installer overwrites all manual changes, for example, rerun for upgrade purposes. If changes are overwritten, you must run the restore procedure to restore the manual changes. For more information, see Restoring Manual Changes Overwritten by a Puppet Run . To view all installer flags available for custom configuration, run satellite-installer --scenario satellite --full-help . Some Puppet classes are not exposed to the Satellite installer. To manage them manually and prevent the installer from overwriting their values, specify the configuration values by adding entries to configuration file /etc/foreman-installer/custom-hiera.yaml . This configuration file is in YAML format, consisting of one entry per line in the format of <puppet class>::<parameter name>: <value> . Configuration values specified in this file persist across installer reruns. Common examples include: For Apache, to set the ServerTokens directive to only return the Product name: To turn off the Apache server signature entirely: The Puppet modules for the Satellite installer are stored under /usr/share/foreman-installer/modules . Check the .pp files (for example: moduleName /manifests/ example .pp) to look up the classes, parameters, and values. Alternatively, use the grep command to do keyword searches. Setting some values may have unintended consequences that affect the performance or functionality of Red Hat Satellite. Consider the impact of the changes before you apply them, and test the changes in a non-production environment first. If you do not have a non-production Satellite environment, run the Satellite installer with the --noop and --verbose options. If your changes cause problems, remove the offending lines from custom-hiera.yaml and rerun the Satellite installer. If you have any specific questions about whether a particular value is safe to alter, contact Red Hat support.

Commands:
apache::server_tokens: Prod
apache::server_signature: Off
Chapter 5. Configuring log settings for Serving and Eventing You can configure logging for OpenShift Serverless Serving and OpenShift Serverless Eventing using the KnativeServing and KnativeEventing custom resource (CR). The level of logging is determined by the specified loglevel value. 5.1. Supported log levels The following loglevel values are supported: Table 5.1. Supported log levels Log level Description debug Fine-grained debugging info Normal logging warn Unexpected but non-critical errors error Critical errors; unexpected during normal operation dpanic In debug mode, trigger a panic (crash) Warning Using the debug level for production might negatively affect performance. 5.2. Configuring log settings You can configure logging for Serving and Eventing in the KnativeServing custom resource (CR) and KnativeEventing CR. Procedure Configure the log settings for Serving and Eventing by setting or modifying the loglevel value in the KnativeServing and KnativeEventing CR respectively. Here are two example configurations with all possible logging options set to level info : KnativeServing CR apiVersion: operator.knative.dev/v1beta1 kind: KnativeServing metadata: name: knative-serving namespace: knative-serving spec: config: logging: loglevel.controller: "info" loglevel.autoscaler: "info" loglevel.queueproxy: "info" loglevel.webhook: "info" loglevel.activator: "info" loglevel.hpaautoscaler: "info" loglevel.net-certmanager-controller: "info" loglevel.net-istio-controller: "info" loglevel.net-kourier-controller: "info" KnativeEventing CR apiVersion: operator.knative.dev/v1beta1 kind: KnativeEventing metadata: name: knative-eventing namespace: knative-eventing spec: config: logging: loglevel.controller: "info" loglevel.eventing-webhook: "info" loglevel.inmemorychannel-dispatcher: "info" loglevel.inmemorychannel-webhook: "info" loglevel.mt-broker-controller: "info" loglevel.mt_broker_filter: "info" loglevel.mt_broker_ingress: "info" loglevel.pingsource-mt-adapter: "info"

Commands:
apiVersion: operator.knative.dev/v1beta1 kind: KnativeServing metadata: name: knative-serving namespace: knative-serving spec: config: logging: loglevel.controller: "info" loglevel.autoscaler: "info" loglevel.queueproxy: "info" loglevel.webhook: "info" loglevel.activator: "info" loglevel.hpaautoscaler: "info" loglevel.net-certmanager-controller: "info" loglevel.net-istio-controller: "info" loglevel.net-kourier-controller: "info"
apiVersion: operator.knative.dev/v1beta1 kind: KnativeEventing metadata: name: knative-eventing namespace: knative-eventing spec: config: logging: loglevel.controller: "info" loglevel.eventing-webhook: "info" loglevel.inmemorychannel-dispatcher: "info" loglevel.inmemorychannel-webhook: "info" loglevel.mt-broker-controller: "info" loglevel.mt_broker_filter: "info" loglevel.mt_broker_ingress: "info" loglevel.pingsource-mt-adapter: "info"
28.6.2. Booting Your Computer with the Rescue Mode You may boot a command-line Linux system from either a rescue disc or an installation disc, without installing Red Hat Enterprise Linux on the computer. This enables you to use the utilities and functions of a running Linux system to modify or repair systems that are already installed on your computer. The rescue disc starts the rescue mode system by default. To load the rescue system with the installation disc, choose Rescue installed system from the boot menu. Specify the language, keyboard layout and network settings for the rescue system with the screens that follow. The final setup screen configures access to the existing system on your computer. By default, rescue mode attaches an existing operating system to the rescue system under the directory /mnt/sysimage/ .

Commands: