mtpti5iD/redhat-docs_dataset huggingface dataset:
Appendix C. Revision History 0.1-2 Fri Apr 28 2023, Lucie Varakova ( lvarakova@redhat.com ) Added a known issue (Authentication and Interoperability). 0.1-1 Tue Mar 02 2021, Lenka Spackova ( lspackova@redhat.com ) Updated a link to Upgrading from RHEL 6 to RHEL 7 . Fixed CentOS Linux name. 0.1-0 Thu Jun 25 2020, Jaroslav Klech ( jklech@redhat.com ) Various improvements to Device Drivers chapter. 0.0-9 Thu Jun 18 2020, Lenka Spackova ( lspackova@redhat.com ) Added a known issue related to Audit (Security). 0.0-8 Thu May 28 2020, Lenka Spackova ( lspackova@redhat.com ) Added the qlcnic and qlge drivers to the list of deprecated drivers. 0.0-7 Tue May 05 2020, Lenka Spackova ( lspackova@redhat.com ) Added an enhancement related to GNOME. 0.0-6 Tue Apr 28 2020, Lenka Spackova ( lspackova@redhat.com ) Updated information about in-place upgrades in Overview. 0.0-5 Fri Apr 3 2020, Lenka Spackova ( lspackova@redhat.com ) Added a known issue (Networking). Added a bug fix (Authentication and Interoperability). Added a deprecated functionality ( NSS SEED ciphers). 0.0-4 Wed Apr 1 2020, Lenka Spackova ( lspackova@redhat.com ) Aero adapters are now fully supported (Hardware Enablement). Added a known issue (Servers and Services). 0.0-3 Tue Mar 31 2020, Lenka Spackova ( lspackova@redhat.com ) Release of the Red Hat Enterprise Linux 7.8 Release Notes. 0.0-2 Wed Feb 12 2020, Lenka Spackova ( lspackova@redhat.com ) Provided a complete kernel version to Architectures and New Features chapters. Various additions and updates to individual release note descriptions. 0.0-1 Mon Feb 03 2020, Lenka Spackova ( lspackova@redhat.com ) Added Important Changes to External Kernel Parameters. Added Device Drivers. Various additions and updates to individual release note descriptions. 0.0-0 Tue Oct 29 2019, Lenka Spackova ( lspackova@redhat.com ) Release of the Red Hat Enterprise Linux 7.8 Beta Release Notes.

Commands:
Part I. Creating a filtered or unfiltered Google Cloud integration Before you create an Google Cloud (GCP) integration, first decide if you want to create a filtered or unfiltered integration. Unfiltered flow An unfiltered integration enables cost management to directly read your billing reports from GCP. You can select the scope of the reports later on. To create an unfiltered integration, go to Creating an unfiltered GCP integration . Filtered flow A filtered integration enables you to customize and filter your data before cost management reads it. Some customers use the filtered integration to share billing data with only certain Red Hat products. It is more complex to set up and configure a filtered integration than an unfiltered one. To create a filtered integration, go to Creating a filtered GCP integration . Note You must create either a filtered or unfiltered integration. Do not follow both sets of instructions.

Commands:
8.3.2. Possible Causes of Silent Denials In certain situations, AVC denials may not be logged when SELinux denies access. Applications and system library functions often probe for more access than required to perform their tasks. To maintain least privilege without filling audit logs with AVC denials for harmless application probing, the policy can silence AVC denials without allowing a permission by using dontaudit rules. These rules are common in standard policy. The downside of dontaudit is that, although SELinux denies access, denial messages are not logged, making troubleshooting more difficult. To temporarily disable dontaudit rules, allowing all denials to be logged, run the following command as the Linux root user: The -D option disables dontaudit rules; the -B option rebuilds policy. After running semodule -DB , try exercising the application that was encountering permission problems, and see if SELinux denials - relevant to the application - are now being logged. Take care in deciding which denials should be allowed, as some should be ignored and handled via dontaudit rules. If in doubt, or in search of guidance, contact other SELinux users and developers on an SELinux list, such as fedora-selinux-list . To rebuild policy and enable dontaudit rules, run the following command as the Linux root user: This restores the policy to its original state. For a full list of dontaudit rules, run the sesearch --dontaudit command. Narrow down searches using the -s domain option and the grep command. For example: Refer to Section 8.3.6, "Raw Audit Messages" and Section 8.3.7, "sealert Messages" for information about analyzing denials.

Commands:
~]# semodule -DB
~]# semodule -B
~]USD sesearch --dontaudit -s smbd_t | grep squid dontaudit smbd_t squid_port_t : tcp_socket name_bind ; dontaudit smbd_t squid_port_t : udp_socket name_bind ;
20.33. Dumping Storage Volume Information to an XML File The virsh vol-dumpxml vol command takes the volume information, creates an XML file with the contents and outputs it to the settings that are set on the stdout stream. Optionally, you can supply the name of the associated storage pool using the --pool option. Example 20.93. How to dump the contents of a storage volume The following example dumps the contents of the storage volume named vol-new into an XML file:

Commands:
virsh vol-dumpxml vol-new
7.79. icu 7.79.1. RHEA-2015:1438 - icu enhancement update Updated icu packages that add one enhancement are now available for Red Hat Enterprise Linux 6. The International Components for Unicode (ICU) library provides robust and full-featured Unicode services. Enhancement BZ# 1200973 Transliteration from Latin to US-ASCII characters is now supported. Prior to this update, icu in Red Hat Enterprise Linux 6 did not support this mode of the transliterator_transliterate() function. Consequently, it was not possible to perform certain operations. For example, the user could not easily remove non-ASCII characters from PHP code strings. With this update, the user can use transliterator_transliterate() to transliterate Latin characters to US-ASCII characters. Users of icu are advised to upgrade to these updated packages, which add this enhancement. 7.79.2. RHBA-2015:0664 - icu bug fix update Updated icu packages that fix one bug are now available for Red Hat Enterprise Linux 6. The International Components for Unicode (ICU) library provides robust and full-featured Unicode services. Bug Fix BZ# 1176177 Previously, during the rebuild process of the icu source package, two-digit format was used for calendar year in the test case and was not interpreted correctly. As a consequence, the year 2034 was displayed instead of year 1934 causing the check of the test case to fail. A patch has been applied to fix this bug and the check no longer fails. Users of icu are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 9. Post-deployment The following subsections describe several post-deployment operations for managing the Ceph cluster. 9.1. Accessing the overcloud The director generates a script to configure and help authenticate interactions with your overcloud from the undercloud. The director saves this file ( overcloudrc ) in your stack user's home directory. Run the following command to use this file: This loads the necessary environment variables to interact with your overcloud from the undercloud CLI. To return to interacting with the undercloud, run the following command: 9.2. Monitoring Ceph Storage nodes After you create the overcloud, check the status of the Ceph Storage Cluster to ensure that it works correctly. Procedure Log in to a Controller node as the heat-admin user: Check the health of the cluster: If the cluster has no issues, the command reports back HEALTH_OK . This means the cluster is safe to use. Log in to an overcloud node that runs the Ceph monitor service and check the status of all OSDs in the cluster: Check the status of the Ceph Monitor quorum: This shows the monitors participating in the quorum and which one is the leader. Verify that all Ceph OSDs are running: For more information on monitoring Ceph Storage clusters, see Monitoring in the Red Hat Ceph Storage Administration Guide .

Commands:
source ~/overcloudrc
source ~/stackrc
nova list ssh heat-admin@192.168.0.25
sudo podman exec ceph-mon-<HOSTNAME> ceph health
sudo podman exec ceph-mon-<HOSTNAME> ceph osd tree
sudo podman exec ceph-mon-<HOSTNAME> ceph quorum_status
sudo podman exec ceph-mon-<HOSTNAME> ceph osd stat
Chapter 30. High Availability Using Server Hinting In Red Hat JBoss Data Grid, Server Hinting ensures that backed up copies of data are not stored on the same physical server, rack, or data center as the original. Server Hinting does not apply to total replication because total replication mandates complete replicas on every server, rack, and data center. Data distribution across nodes is controlled by the Consistent Hashing mechanism. JBoss Data Grid offers a pluggable policy to specify the consistent hashing algorithm. For details see Section 30.4, "ConsistentHashFactories" Setting a machineId , rackId , or siteId in the transport configuration will trigger the use of TopologyAwareConsistentHashFactory , which is the equivalent of the DefaultConsistentHashFactory with Server Hinting enabled. Server Hinting is particularly important when ensuring the high availability of your JBoss Data Grid implementation. Report a bug 30.1. Establishing Server Hinting with JGroups When setting up a clustered environment in Red Hat JBoss Data Grid, Server Hinting is configured when establishing JGroups configuration. JBoss Data Grid ships with several JGroups files pre-configured for clustered mode. These files can be used as a starting point when configuring Server Hinting in JBoss Data Grid. See Also: Section 26.2.2, "Pre-Configured JGroups Files" Report a bug

Commands:
Chapter 280. Example: PetStore Checkout the example in the camel-example-rest-openapi project in the examples directory. For example if you wanted to use the PetStore provided REST API simply reference the specification URI and desired operation id from the OpenApi specification or download the specification and store it as openapi.json (in the root) of CLASSPATH that way it will be automaticaly used. Let's use the Undertow component to perform all the requests and Camels excelent support for Spring Boot. Here are our dependencies defined in Maven POM file: <dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-undertow-starter</artifactId> </dependency> <dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-rest-openapi-starter</artifactId> </dependency> Start by defining the Undertow component and the RestOpenApiComponent : @Bean public Component petstore(CamelContext camelContext, UndertowComponent undertow) { RestOpenApiComponent petstore = new RestOpenApiComponent(camelContext); petstore.setSpecificationUri("https://petstore3.swagger.io/api/v3/openapi.json"); petstore.setDelegate(undertow); return petstore; } Note Support in Camel for Spring Boot will auto create the UndertowComponent Spring bean, and you can configure it using application.properties (or application.yml ) using prefix camel.component.undertow. . We are defining the petstore component here in order to have a named component in the Camel context that we can use to interact with the PetStore REST API, if this is the only rest-openapi component used we might configure it in the same manner (using application.properties ). Now in our application we can simply use the ProducerTemplate to invoke PetStore REST methods: @Autowired ProducerTemplate template; String getPetJsonById(int petId) { return template.requestBodyAndHeaders("petstore:getPetById", null, "petId", petId); }

Commands:
<dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-undertow-starter</artifactId> </dependency> <dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-rest-openapi-starter</artifactId> </dependency>
@Bean public Component petstore(CamelContext camelContext, UndertowComponent undertow) { RestOpenApiComponent petstore = new RestOpenApiComponent(camelContext); petstore.setSpecificationUri("https://petstore3.swagger.io/api/v3/openapi.json"); petstore.setDelegate(undertow); return petstore; }
@Autowired ProducerTemplate template; String getPetJsonById(int petId) { return template.requestBodyAndHeaders("petstore:getPetById", null, "petId", petId); }
Chapter 10. Supported and Unsupported features for IBM Power and IBM Z infrastructure Table 10.1. List of supported and unsupported features on IBM Power and IBM Z infrastructure Features IBM Power IBM Z infrastructure Compact deployment Unsupported Unsupported Dynamic storage devices Unsupported Supported Metro-DR (Stretched Cluster - Arbiter) Unsupported Unsupported External mode Unsupported Unsupported FIPS Unsupported Unsupported Ability to view pool compression metrics Supported Unsupported Automated scaling of Multicloud Object Gateway endpoint pods Supported Unsupported Alerts to control overprovision Supported Unsupported Alerts when Ceph Monitor runs out of space Supported Unsupported Deployment of standalone Multicloud Object Gateway component Supported Unsupported Extended OpenShift Data Foundation control plane which allows pluggable external storage such as IBM Flashsystem Unsupported Unsupported IPV6 support Unsupported Unsupported Multus Unsupported Unsupported Multicloud Object Gateway bucket replication Supported Unsupported Quota support for object data Supported Unsupported Regional-DR with Red Hat Advanced Cluster Management (RHACM) Unsupported Unsupported Minimum deployment Unsupported Unsupported

Commands:
11.2. Email Program Classifications In general, all email applications fall into at least one of three classifications. Each classification plays a specific role in the process of moving and managing email messages. While most users are only aware of the specific email program they use to receive and send messages, each one is important for ensuring that email arrives at the correct destination. 11.2.1. Mail Transfer Agent A Mail Transfer Agent ( MTA ) transfers email messages between hosts using SMTP. A message may involve several MTAs as it moves to its intended destination. While the delivery of messages between machines may seem rather straightforward, the entire process of deciding if a particular MTA can or should accept a message for delivery is quite complicated. In addition, due to problems from spam, use of a particular MTA is usually restricted by the MTA's configuration or the access configuration for the network on which the MTA resides. Many modern email client programs can act as an MTA when sending email. However, this action should not be confused with the role of a true MTA. The sole reason email client programs are capable of sending email like an MTA is because the host running the application does not have its own MTA. This is particularly true for email client programs on non-UNIX-based operating systems. However, these client programs only send outbound messages to an MTA they are authorized to use and do not directly deliver the message to the intended recipient's email server. Since Red Hat Enterprise Linux installs two MTAs, Sendmail and Postfix, email client programs are often not required to act as an MTA. Red Hat Enterprise Linux also includes a special purpose MTA called Fetchmail. For more information on Sendmail, Postfix, and Fetchmail, refer to Section 11.3, "Mail Transport Agents" .

Commands:
1.4.2. Runlevel Utilities One of the best ways to configure runlevels is to use an initscript utility . These tools are designed to simplify the task of maintaining files in the SysV init directory hierarchy and relieves system administrators from having to directly manipulate the numerous symbolic links in the subdirectories of /etc/rc.d/ . Red Hat Enterprise Linux provides three such utilities: /sbin/chkconfig - The /sbin/chkconfig utility is a simple command line tool for maintaining the /etc/rc.d/init.d/ directory hierarchy. /usr/sbin/ntsysv - The ncurses-based /sbin/ntsysv utility provides an interactive text-based interface, which some find easier to use than chkconfig . Services Configuration Tool - The graphical Services Configuration Tool ( system-config-services ) program is a flexible utility for configuring runlevels. Refer to the chapter titled Controlling Access to Services in the System Administrators Guide for more information regarding these tools.

Commands:
Chapter 5. Running .NET 6.0 applications in containers Use the ubi8/dotnet-60-runtime image to run a precompiled application inside a Linux container. Prerequisites Preconfigured containers. The following example uses podman. Procedure Optional: If you are in another project's directory and do not wish to create a nested project, return to the parent directory of the project: Create a new MVC project in a directory called mvc_runtime_example : Publish the project: Create the Dockerfile : Build your image: Run your image: Verification steps View the application running in the container:

Commands:
cd ..
dotnet new mvc --output mvc_runtime_example
dotnet publish mvc_runtime_example -f net6.0 -c Release
cat > Dockerfile <<EOF FROM registry.redhat.io/ubi8/dotnet-60-runtime ADD bin/Release/net6.0/publish/ . CMD ["dotnet", "mvc_runtime_example.dll"] EOF
podman build -t dotnet-60-runtime-example .
podman run -d -p8080:8080 dotnet-60-runtime-example
xdg-open http://127.0.0.1:8080
8.5. Release Notes 8.5.1. RHEA-2014:1608 - Red Hat Enterprise Linux 6.6 Release Notes Updated packages containing the Release Notes for Red Hat Enterprise Linux 6.6 are now available. Red Hat Enterprise Linux minor releases are an aggregation of individual enhancement, security and bug fix errata. The Red Hat Enterprise Linux 6.6 Release Notes documents the major changes made to the Red Hat Enterprise Linux 6 operating system and its accompanying applications for this minor release. Detailed notes on all changes in this minor release are available in the Technical Notes. Refer to the Online Release Notes for the most up-to-date version of the Red Hat Enterprise Linux 6.6 Release Notes: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/ht ml-single/6.6_Release_Notes/index.html

Commands:
Common object reference OpenShift Container Platform 4.16 Reference guide common API objects Red Hat OpenShift Documentation Team

Commands:
<quantity> ::= <signedNumber><suffix>
(Note that <suffix> may be empty, from the "" case in <decimalSI>.)
(International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)
(Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)
type MyAPIObject struct { runtime.TypeMeta `json:",inline"` MyPlugin runtime.Object `json:"myPlugin"` }
type PluginA struct { AOption string `json:"aOption"` }
type MyAPIObject struct { runtime.TypeMeta `json:",inline"` MyPlugin runtime.RawExtension `json:"myPlugin"` }
type PluginA struct { AOption string `json:"aOption"` }
{ "kind":"MyAPIObject", "apiVersion":"v1", "myPlugin": { "kind":"PluginA", "aOption":"foo", }, }
5.3. Resizing an ext4 File System Before growing an ext4 file system, ensure that the underlying block device is of an appropriate size to hold the file system later. Use the appropriate resizing methods for the affected block device. An ext4 file system may be grown while mounted using the resize2fs command: The resize2fs command can also decrease the size of an unmounted ext4 file system: When resizing an ext4 file system, the resize2fs utility reads the size in units of file system block size, unless a suffix indicating a specific unit is used. The following suffixes indicate specific units: s - 512 byte sectors K - kilobytes M - megabytes G - gigabytes Note The size parameter is optional (and often redundant) when expanding. The resize2fs automatically expands to fill all available space of the container, usually a logical volume or partition. For more information about resizing an ext4 file system, refer to man resize2fs .

Commands:
resize2fs /mount/device size
resize2fs /dev/ device size
5.2.13. /proc/ioports The output of /proc/ioports provides a list of currently registered port regions used for input or output communication with a device. This file can be quite long. The following is a partial listing: The first column gives the I/O port address range reserved for the device listed in the second column.

Commands:
0000-001f : dma1 0020-003f : pic1 0040-005f : timer 0060-006f : keyboard 0070-007f : rtc 0080-008f : dma page reg 00a0-00bf : pic2 00c0-00df : dma2 00f0-00ff : fpu 0170-0177 : ide1 01f0-01f7 : ide0 02f8-02ff : serial(auto) 0376-0376 : ide1 03c0-03df : vga+ 03f6-03f6 : ide0 03f8-03ff : serial(auto) 0cf8-0cff : PCI conf1 d000-dfff : PCI Bus #01 e000-e00f : VIA Technologies, Inc. Bus Master IDE e000-e007 : ide0 e008-e00f : ide1 e800-e87f : Digital Equipment Corporation DECchip 21140 [FasterNet] e800-e87f : tulip
probe::netfilter.ip.local_out Name probe::netfilter.ip.local_out - Called on an outgoing IP packet Synopsis netfilter.ip.local_out Values dport TCP or UDP destination port (ipv4 only) nf_queue Constant used to signify a 'queue' verdict syn TCP SYN flag (if protocol is TCP; ipv4 only) ipproto_udp Constant used to signify that the packet protocol is UDP ack TCP ACK flag (if protocol is TCP; ipv4 only) fin TCP FIN flag (if protocol is TCP; ipv4 only) iphdr Address of IP header saddr A string representing the source IP address sport TCP or UDP source port (ipv4 only) indev Address of net_device representing input device, 0 if unknown nf_drop Constant used to signify a 'drop' verdict daddr A string representing the destination IP address pf Protocol family -- either " ipv4 " or " ipv6 " psh TCP PSH flag (if protocol is TCP; ipv4 only) urg TCP URG flag (if protocol is TCP; ipv4 only) length The length of the packet buffer contents, in bytes nf_stolen Constant used to signify a 'stolen' verdict ipproto_tcp Constant used to signify that the packet protocol is TCP indev_name Name of network device packet was received on (if known) nf_repeat Constant used to signify a 'repeat' verdict family IP address family outdev Address of net_device representing output device, 0 if unknown outdev_name Name of network device packet will be routed to (if known) nf_accept Constant used to signify an 'accept' verdict nf_stop Constant used to signify a 'stop' verdict rst TCP RST flag (if protocol is TCP; ipv4 only) protocol Packet protocol from driver (ipv4 only)

Commands:
7.87. iputils 7.87.1. RHBA-2015:1251 - iputils bug fix update Updated iputils packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The iputils packages contain basic utilities for monitoring a network, including ping. Bug Fixes BZ# 829998 The arping command previously returned incorrect exit codes in some cases due to incorrect time related logic and exit-handling conditions in the code. With this update, the aforementioned problems have been fixed, and arping again returns correct values. BZ# 1099426 Due to incorrect code that handles the number of return path hops, the tracepath utility displayed an incorrect number of "back" hops. This update fixes the logic, and the number of displayed back hops is now accurate. BZ# 1113082 When domain name translation was forced to be carried out over the IPv6 protocol, the output of the "ping" command was incorrect as it displayed an incorrect IP address received from the internal library. The underlying logic has been modified to use the gethostbyname2() function instead of gethostbyname(), and domain name to IP address translation now works correctly. BZ# 1149574 Due to invalid logic present in the code, an erroneous warning message could be returned under certain circumstances: WARNING: kernel is not very fresh, upgrade is recommended. This update removes the code responsible for returning this erroneous warning message, thus fixing the bug. Users of iputils are advised to upgrade to these updated packages, which fix these bugs.

Commands: