Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 754615

Summary: Remove "and" from the end of the paragraph.
Product: Red Hat Enterprise Linux 6 Reporter: cshao <cshao>
Component: DocumentationAssignee: Laura Bailey <lbailey>
Status: CLOSED NOTABUG QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: apevec, gouyang, leiwang, mburns, moli, ycui
Target Milestone: rcKeywords: Documentation
Target Release: 6.2   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-17 03:34:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description cshao 2011-11-17 02:44:30 UTC 
Description of problem:

The word "and" shouldn't appear at the end of the paragraph, please remove it.
Fields marked with an asterisk (******) are mistake.

1. On page:
http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html/Hypervisor_Deployment_Guide/sect-Deployment_Guide-Red_Hat_Enterprise_Virtualization_Hypervisor_interactive_installation-Configuration-Status.html


      the hostname,

      the current status of the network connection,

      the destination(s) of logs and reports, ******and******

      the number of active virtual machines. 

2. On page:
http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html/Hypervisor_Deployment_Guide/sect-Deployment_Guide-Red_Hat_Enterprise_Virtualization_Hypervisor_interactive_installation-Configuration-Network.html
   1)
      the Hypervisor's hostname,

      the DNS server(s) to use,

      the NTP server(s) to use, ******and******

      the network interface to use. 


   2)
Procedure 5.4. Network Interface Configuration
For each network interface detected the Hypervisor will display the:


      Device,

      Status,

      Model, ******and******

      MAC Address. 

   3)
Device Identification
Select the network interface to be configured from the list and press Enter.
In some cases it may be unclear which physical device an entry in the list refers to. Where this is the case the Hypervisor is able to blink the physical device's network traffic lights to assist with identification. To make use of this facility select the entry from the list ******and******, then select the <Flash Lights to Identify> button. Press Enter ******and******, take note of which physical device's lights start blinking. The configuration screen for the selected device will be displayed. 

   4)
In particular it is necessary that:

      the IP Address is not already in use on the network,

      the Netmask matches that used by other machines on the network, ******and******

      the Gateway matches that used by other machines on the network. 


3. On page:
http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html/Hypervisor_Deployment_Guide/sect-Deployment_Guide-Red_Hat_Enterprise_Virtualization_Hypervisor_interactive_installation-Configuration-Remote_Storage.html

The IQN is made up of the following elements, separated by the . character:


      the literal string iqn,

      the date that the naming authority took control of the domain in yyyy-mm format,

      the reversed domain name - demo.redhat.com becomes com.redhat.demo, ******and******

      optionally, a storage target name as specified by the naming authority - preceded by a colon. 


4. On page:
http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html/Hypervisor_Deployment_Guide/sect-Deployment_Guide-Red_Hat_Enterprise_Virtualization_Hypervisor_interactive_installation-Configuration-RHN.html

HTTP Proxy
Where a HTTP proxy is in use the details to connect to it must be provided. To connect to the Red Hat Network or a Satellite server via a proxy you must enter:


      the proxy Server's network address,

      the Port to connect to the proxy on, ******and******

      optionally, the Username and Password to use to connect to the proxy.