Bug 610112 - Missing words in LVM
Summary: Missing words in LVM
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: Red_Hat_Enterprise_Linux-Release_Notes-6-en-US
Version: 6.0
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Ryan Lerch
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-01 15:18 UTC by Chris Pepper
Modified: 2010-11-11 15:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-11 15:24:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Chris Pepper 2010-07-01 15:18:23 UTC
Description of problem:
What manages logical volumes?

Version-Release number of selected component (if applicable):
6b2

How reproducible:
http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html/Beta_2_Release_Notes/storage.html
Actual results:
In Red Hat Enterprise Linux 6 Beta, manages logical volumes using the Logical Volume Manager (LVM).
 
Expected results:
In Red Hat Enterprise Linux 6 Beta, ??? manages logical volumes using the Logical Volume Manager (LVM).
Red Hat Enterprise Linux 6 Beta manages logical volumes using the Logical Volume Manager (LVM).

Comment 2 RHEL Program Management 2010-07-01 15:43:16 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 Ryan Lerch 2010-07-09 03:43:37 UTC
Chris,

Thanks for taking the time to file this bug, i have now fixed this issue, the
change will be visible the next time the release notes are refreshed on
redhat.com/docs

cheers,
ryanlerch

Comment 7 releng-rhel@redhat.com 2010-11-11 15:24:39 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.