mtpti5iD/redhat-docs_dataset huggingface dataset:
5.102. hivex 5.102.1. RHBA-2012:0776 - hivex bug fix and enhancement update Updated hivex packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. Hive files are undocumented binary files that Windows uses to store the Windows Registry on the disk. Hivex is a library that can read and write to these files. The hivex packages have been upgraded to upstream version 1.3.3, which provides a number of bug fixes and enhancements over the version. (BZ# 734208 ) All hivex users are advised to upgrade to these updated hivex packages, which fix these bugs and add these enhancements.

Commands:
Chapter 6. Resolved issues The following issues are resolved for this release: Issue Description JWS-3213 [OpenShift doc] Replace old example repository JWS-3211 Remove tomcat-8-valves-1.0.3.Final-redhat-1.jar from JWS 6 container image JWS-3209 Doc: Typo "oc env" "oc set env" in JWS for OpenShift guide for version 6.0 JWS-3208 Doc: Different texts in 6.0 doc when configuring folder permissions for JBoss Web Server services on Microsoft Windows JWS-3132 [ASF BZ 67938] Tomcat mishandles large client hello messages

Commands:
Chapter 6. Red Hat build of OpenJDK MSI installer components The Red Hat build of OpenJDK 8 for Microsoft Windows MSI-based installer includes the following components: jdk Runtime environment files (excluding development tools). jdk_devel Java Development Kit files. jdk_registry_standard Registry keys: jdk_registry_standard_devel Registry keys: jdk_env_path Appends <INSTALLDIR>\bin and <INSTALLDIR>\jre\bin to the system %PATH% environment variable. jdk_env_java_home Sets <INSTALLDIR> to the system %JAVA_HOME% environment variable. jdk_env_vendor_java_home Sets <INSTALLDIR> to the system %REDHAT_JAVA_HOME% environment variable. jdk_registry_jar Association for JAR files. Launch JAR files using the Red Hat build of OpenJDK context menu. jmc JDK Mission Control Files. jmc_env Appends `<jdk>/missioncontrol to the 'PATH' system environment variable. webstart WebStart files, installed into <INSTALLDIR>\webstart . webstart_registry Association for JNLP files and jnlp:// URLs. webstart_env Appends <INSTALLDIR>\webstart to the system %PATH% environment variable. webstart_migrate Migrate WebStart local settings and cache on update. webstart_plugin Installs plugin.jar into <jdk>/jre/lib/ for compatibility with third-party applications. Web browser plugin implementation is not included.

Commands:
HKLM\Software\JavaSoft\Java Runtime Environment, entries: CurrentVersion: 1.8 HKLM\Software\JavaSoft\Java Runtime Environment\1.8, entries: JavaHome: <INSTALLDIR>\jre RuntimeLib: <INSTALLDIR>\jre\bin\server\jvm.dll HKLM\Software\JavaSoft\Java Runtime Environment\1.8_<update>, entries: JavaHome: <INSTALLDIR>\jre RuntimeLib: <INSTALLDIR>\jre\bin\server\jvm.dll
HKLM\Software\JavaSoft\Java Development Kit, entries: CurrentVersion: 1.8 HKLM\Software\JavaSoft\Java Development Kit\1.8, entries: JavaHome: <INSTALLDIR> RuntimeLib: <INSTALLDIR>\jre\bin\server\jvm.dll HKLM\Software\JavaSoft\Java Development Kit\1.8_<update>, entries: JavaHome: <INSTALLDIR> RuntimeLib: <INSTALLDIR>\jre\bin\server\jvm.dll
function::ansi_cursor_move Name function::ansi_cursor_move - Move cursor to new coordinates. Synopsis Arguments x Row to move the cursor to. y Colomn to move the cursor to. General Syntax ansi_curos_move(x:long, y:long) Description Sends ansi code for positioning the cursor at row x and column y. Coordinates start at one, (1,1) is the top-left corner.

Commands:
function ansi_cursor_move(x:long,y:long)
Chapter 9. Desktop and Graphics New Package: gdk-pixbuf2 The gdk-pixbuf2 package, previously a part of the gtk2 package, has been added to Red Hat Enterprise Linux 6.6. The gdk-pixbuf2 package contains an image-loading library that can be extended by loadable modules for new image formats. The library is used by toolkits such as GTK+ or Clutter. Note that downgrading the libraries included in the gdk-pixbuf2 and gtk2 packages can fail.

Commands:
Part III. Online Storage The Online Storage section covers how to set up and manage iSCSI and FCoE storage connections. Online storage reconfiguration must be done carefully. System failures or interruptions during the process can lead to unexpected results. Red Hat advises that you reduce system load to the maximum extent possible during the change operations. This will reduce the chance of I/O errors, out-of-memory errors, or similar errors occurring in the midst of a configuration change. The following sections provide more specific guidelines regarding this. In addition, Red Hat recommends that you back up all data before reconfiguring online storage.

Commands:
5.7.4.2.2. Erase the Contents of the Disk Drive No matter whether the disk drive has valuable data or not, it is a good idea to always erase a disk drive's contents prior to reassigning or relinquishing control of it. While the obvious reason is to make sure that no sensitive information remains on the disk drive, it is also a good time to check the disk drive's health by performing a read-write test for bad blocks over the entire drive. Important Many companies (and government agencies) have specific methods of erasing data from disk drives and other data storage media. You should always be sure you understand and abide by these requirements; in many cases there are legal ramifications if you fail to do so. The example above should in no way be considered the ultimate method of wiping a disk drive. In addition, organizations that work with classified data may find that the final disposition of the disk drive may be subject to certain legally-mandated procedures (such as physical destruction of the drive). In these instances your organization's security department should be able to offer guidance in this matter.

Commands:
Chapter 1. About disconnected environments A disconnected environment is an environment that does not have full access to the internet. OpenShift Container Platform is designed to perform many automatic functions that depend on an internet connection, such as retrieving release images from a registry or retrieving update paths and recommendations for the cluster. Without a direct internet connection, you must perform additional setup and configuration for your cluster to maintain full functionality in the disconnected environment. 1.1. Glossary of disconnected environment terms Although it is used throughout the OpenShift Container Platform documentation, disconnected environment is a broad term that can refer to environments with various levels of internet connectivity. Other terms are sometimes used to refer to a specific level of internet connectivity, and these environments might require additional unique configurations. The following table describes the different terms used to refer to environments without a full internet connection: Table 1.1. Disconnected environment terms Term Description Air-gapped network An environment or network that is completely isolated from an external network. This isolation depends on a physical separation, or an "air gap", between machines on the internal network and any other part of an external network. Air-gapped environments are often used in industries with strict security or regulatory requirements. Disconnected environment An environment or network that has some level of isolation from an external network. This isolation could be enabled by physical or logical separation between machines on the internal network and an external network. Regardless of the level of isolation from the external network, a cluster in a disconnected environment does not have access to public services hosted by Red Hat and requires additional setup to maintain full cluster functionality. Restricted Network An environment or network with limited connection to an external network. A physical connection may exist between machines on the internal network and an external network, but network traffic is limited by additional configurations, such as with firewalls and proxies. 1.2. Preferred methods for working with disconnected environments You can choose between multiple options for most aspects of managing a cluster in a disconnected environment. For example, when mirroring images you can choose between using the oc-mirror OpenShift CLI ( oc ) plugin or using the oc adm command. However, some options provide a simpler and more convenient user experience for disconnected environments, and are the preferred method over their alternatives. Unless your organizational needs require you to choose another option, use the following methods for mirroring images, installing your cluster, and updating your cluster: Mirror your images using the oc-mirror plugin v2 . Install your cluster using the Agent-based Installer . Update your cluster using a local OpenShift Update Service instance .

Commands:
Preface Red Hat OpenStack Platform provides the foundation to build a private or public cloud on top of Red Hat Enterprise Linux. It offers a massively scalable, fault-tolerant platform for the development of cloud-enabled workloads. This guide describes the steps to plan and configure single root input/output virtualization(SR-IOV) and Open vSwitch with Data Plane Development Kit (OVS-DPDK) using the Red Hat OpenStack Platform director for NFV deployments.

Commands:
5.80. gd 5.80.1. RHBA-2012:1274 - gd bug fix update Updated gd packages that fix one bug is now available for Red Hat Enterprise Linux 6. The gd packages provide the gd graphics library. GD allows code to draw images as PNG or JPEG files. Bug Fix BZ# 790400 Prior to this update, ,the gd graphics library handled inverted Y coordinates incorrectly, when changing the thickness of a line. As a consequence, lines with changed thickness were drawn incorrectly. This update modifies the underlying code to draw lines with changed thickness correctly. All users of gd are advised to upgrade to these updated packages, which fix this bug.

Commands:
8.41. febootstrap 8.41.1. RHBA-2013:1535 - febootstrap bug fix update Updated febootstrap packages that fix one bug are now available for Red Hat Enterprise Linux 6. The febootstrap package is used by libguestfs to build a small appliance. Note The febootstrap package has been upgraded to upstream version 3.21, which provides one bug fix over the version. Bug Fix BZ# 902478 Previously, when using febootstrap-supermin-helper with the "-g" option, the command did not set the supplemental groups properly. As a consequence, some groups from the user running libguestfs leaked into the appliance build process. After this update, supplemental groups are set correctly. Users of febootstrap are advised to upgrade to these updated packages, which fix this bug.

Commands:
B.62. openssl B.62.1. RHSA-2010:0888 - Important: openssl security update Updated openssl packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link(s) associated with each description below. OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols, as well as a full-strength, general purpose cryptography library. CVE-2010-3864 A race condition flaw has been found in the OpenSSL TLS server extension parsing code, which could affect some multithreaded OpenSSL applications. Under certain specific conditions, it may be possible for a remote attacker to trigger this race condition and cause such an application to crash, or possibly execute arbitrary code with the permissions of the application. Note Note that this issue does not affect the Apache HTTP Server. Refer to Red Hat Bugzilla bug 649304 for more technical details on how to determine if your application is affected. Red Hat would like to thank Rob Hulswit for reporting this issue. All OpenSSL users should upgrade to these updated packages, which contain a backported patch to resolve this issue. For the update to take effect, all services linked to the OpenSSL library must be restarted, or the system rebooted.

Commands:
1.5. Searching To execute a search, create a Lucene query (see Section 5.1.1, "Building a Lucene Query Using the Lucene-based Query API" ). Wrap the query in a org.infinispan.query.CacheQuery to get the required functionality from the Lucene-based API. The following code prepares a query against the indexed fields. Executing the code returns a list of Book s. Example 1.1. Using Infinispan Query to Create and Execute a Search Report a bug

Commands:
QueryBuilder qb = Search.getSearchManager(cache).buildQueryBuilderForClass(Book.class).get(); org.apache.lucene.search.Query query = qb .keyword() .onFields("title", "author") .matching("Java rocks!") .createQuery(); // wrap Lucene query in a org.infinispan.query.CacheQuery CacheQuery cacheQuery = Search.getSearchManager(cache).getQuery(query); List list = cacheQuery.list();
20.16.9.4. User-space SLIRP stack Setting the user-space SLIRP stack parameters provides a virtual LAN with NAT to the outside world. The virtual network has DHCP and DNS services and will give the guest virtual machine an IP addresses starting from 10.0.2.15. The default router will be 10.0.2.2 and the DNS server will be 10.0.2.3. This networking is the only option for unprivileged users who need their guest virtual machines to have outgoing access. The user-space SLIP stack parameters are defined in the following part of the domain XML:: ... <devices> <interface type='user'/> ... <interface type='user'> <mac address="00:11:22:33:44:55"/> </interface> </devices> ... Figure 20.39. Devices - network interfaces- User-space SLIRP stack

Commands:
<devices> <interface type='user'/> <interface type='user'> <mac address="00:11:22:33:44:55"/> </interface> </devices>
Appendix A. Using Your Subscription AMQ Streams is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. 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 Streams entries in the JBOSS INTEGRATION AND AUTOMATION category. Select the desired AMQ Streams product. The Software Downloads page opens. Click the Download link for your component. Revised on 2020-12-02 15:51:39 UTC

Commands:
5.245. pki-core 5.245.1. RHBA-2012:0761 - pki-core bug fix update Updated pki-core packages that fix several bugs are now available for Red Hat Enterprise Linux 6. Red Hat Certificate System is an enterprise software system designed to manage enterprise public key infrastructure (PKI) deployments. PKI Core contains fundamental packages required by Red Hat Certificate System, which comprise the Certificate Authority (CA) subsystem. Note: The Certificate Authority component provided by this advisory cannot be used as a standalone server. It is installed and operates as a part of the Red Hat Enterprise Identity (IPA). Bug Fixes BZ# 745677 A Firefox launcher setting which opened a non-functional Certificate Authority (CA) page was improperly created and applied to all user profiles. With this update, all PKI-related desktop icons have been removed and the problem no longer occurs. BZ# 769388 The pkisilent script did not accept special shell characters, such as spaces or quotation marks, in argument values even if they were properly escaped. Consequently, errors occurred and the script failed. This update improves the code and the problem no longer occurs. BZ# 771790 When installing IPA, the installer uses the "sslget" utility to communicate with the CA. Due to a change in Network Security Services (NSS), the server sent out a full response to the sslget client consisting of 9906 bytes but the client received only 5 bytes of the encrypted stream. With this update the problem is fixed and sslget now prints the returned XML form from the PKI CA as expected. BZ# 806046 Tomcat has changed the way the server startup is logged. In versions, server startup and operation was written to the catalina.out file by the root and tomcat users. Now, the root and tomcat users write to different logs. After the change, the Certificate System (CS) tomcat subsystems failed to start due to incorrect permissions. The CS startup code has been modified to reflect this new logging and now works as expected. All users of pki-core are advised to upgrade to these updated packages, which fix these bugs.

Commands:
8.2. Manual LVM Partitioning The following section explains how to manually configure LVM for Red Hat Enterprise Linux. Because there are numerous ways to manually configure a system with LVM, the following example is similar to the default configuration done in Section 8.1, "Automatic Partitioning" . On the Disk Partitioning Setup screen, select Manually partition with Disk Druid . 8.2.1. Creating the /boot/ Partition In a typical situation, the disk drives are new, or formatted clean. The following figure, Figure 8.2, "Two Blank Drives, Ready For Configuration" , shows both drives as raw devices with no partitioning configured. Figure 8.2. Two Blank Drives, Ready For Configuration Warning The /boot/ partition cannot reside on an LVM volume group because the GRUB boot loader cannot read it. Select New . Select /boot from the Mount Point pulldown menu. Select ext3 from the File System Type pulldown menu. Select only the sda checkbox from the Allowable Drives area. Leave 100 (the default) in the Size (MB) menu. Leave the Fixed size (the default) radio button selected in the Additional Size Options area. Select Force to be a primary partition to make the partition be a primary partition. A primary partition is one of the first four partitions on the hard drive. If unselected, the partition is created as a logical partition. If other operating systems are already on the system, unselecting this option should be considered. For more information on primary versus logical/extended partitions, refer to the appendix section of the Installation Guide . Refer to Figure 8.3, "Creation of the Boot Partition" to verify your inputted values: Figure 8.3. Creation of the Boot Partition Click OK to return to the main screen. The following figure displays the boot partition correctly set: Figure 8.4. The /boot/ Partition Displayed

Commands:
Chapter 1. About Red Hat OpenShift Dev Spaces Red Hat OpenShift Dev Spaces provides web-based development environments on Red Hat OpenShift with an enterprise-level setup: Cloud Development Environments (CDE) server IDEs such as Microsoft Visual Studio Code - Open Source and JetBrains IntelliJ IDEA Community ( Technology Preview ) Containerized environments with popular programming languages, frameworks, and Red Hat technologies Red Hat OpenShift Dev Spaces is well-suited for container-based development. Red Hat OpenShift Dev Spaces 3.15 is based on Eclipse Che 7.88. 1.1. Supported platforms OpenShift Dev Spaces runs on OpenShift 4.12-4.16 on the following CPU architectures: AMD64 and Intel 64 ( x86_64 ) IBM Z ( s390x ) The following CPU architecture requires Openshift 4.13-4.16 to run OpenShift Dev Spaces: IBM Power ( ppc64le ) Additional resources OpenShift Documentation Red Hat OpenShift Dev Spaces administration guide 1.2. Support policy For Red Hat OpenShift Dev Spaces 3.15, Red Hat will provide support for deployment, configuration, and use of the product. Additional resources OpenShift Dev Spaces life-cycle and support policy . 1.3. Differences between Red Hat OpenShift Dev Spaces and Eclipse Che There are some differences between Red Hat OpenShift Dev Spaces and the upstream project on which it is based, Eclipse Che: OpenShift Dev Spaces is supported only on Red Hat OpenShift. OpenShift Dev Spaces is based on Red Hat Enterprise Linux and is regularly updated to include the latest security fixes. OpenShift Dev Spaces provides devfiles for working with languages and technologies such as Quarkus, Lombok, NodeJS, Python, DotNet, Golang, C/C++, and PHP. You can find the latest sample projects in the devspaces-devfileregistry container image sources . OpenShift Dev Spaces uses OpenShift OAuth for user login and management. Red Hat provides licensing and packaging to ensure enterprise-level support for OpenShift Dev Spaces.

Commands:
Deploying and managing OpenShift Data Foundation using Red Hat OpenStack Platform Red Hat OpenShift Data Foundation 4.13 Instructions on deploying and managing OpenShift Data Foundation on Red Hat OpenStack Platform Red Hat Storage Documentation Team Abstract Read this document for instructions about how to install and manage Red Hat OpenShift Data Foundation using Red Hat OpenShift Container Platform on Red Hat OpenStack Platform (RHOSP). Important Deploying and managing OpenShift Data Foundation on Red Hat OpenStack Platform is a Technology Preview feature. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

Commands:
Chapter 1. The Philosophy of System Administration Although the specifics of being a system administrator may change from platform to platform, there are underlying themes that do not. These themes make up the philosophy of system administration. The themes are: Automate everything Document everything Communicate as much as possible Know your resources Know your users Know your business Security cannot be an afterthought Plan ahead Expect the unexpected The following sections explore each theme in more detail. 1.1. Automate Everything Most system administrators are outnumbered -- either by their users, their systems, or both. In many cases, automation is the only way to keep up. In general, anything done more than once should be examined as a possible candidate for automation. Here are some commonly automated tasks: Free disk space checking and reporting Backups System performance data collection User account maintenance (creation, deletion, etc.) Business-specific functions (pushing new data to a Web server, running monthly/quarterly/yearly reports, etc.) This list is by no means complete; the functions automated by system administrators are only limited by an administrator's willingness to write the necessary scripts. In this case, being lazy (and making the computer do more of the mundane work) is actually a good thing. Automation also gives users the extra benefit of greater predictability and consistency of service. Note Keep in mind that if you have a task that should be automated, it is likely that you are not the first system administrator to have that need. Here is where the benefits of open source software really shine -- you may be able to leverage someone else's work to automate the manual procedure that is currently eating up your time. So always make sure you search the Web before writing anything more complex than a small Perl script.

Commands: