Bug 587995 - Correction: Incorrect path to multipath doc files
Summary: Correction: Incorrect path to multipath doc files
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-DM_Multipath
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Steven J. Levine
QA Contact: ecs-bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-02 02:31 UTC by Justin Clift
Modified: 2010-11-11 15:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-11-11 15:27:40 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Justin Clift 2010-05-02 02:31:27 UTC
Description of problem:

In "Chapter 4. The DM-Multipath Configuration File", it gives explicit paths to the example multipath files installed on RHEL x.

However, in the RHEL 6 version of the guide, this is wrong.

Explicit paths mentioned:


The actual paths in the present RHEL 6 beta are:


(It's not just the version number, there's an extra "d" in the path too)

Comment 2 RHEL Program Management 2010-05-02 03:22:28 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

Comment 4 Steven J. Levine 2010-09-20 21:48:10 UTC
I have updated the references to these paths in the RHEL 6 working draft of the DM-Multipath document. Thanks for catching this.

Comment 5 Steven J. Levine 2010-10-12 20:34:39 UTC
I am marking this bug as MODIFIED since the changes have been checked in to the SVN repository and posted on the review server.

Comment 7 Michael Doyle 2010-10-15 03:25:30 UTC
Verified in Red_Hat_Enterprise_Linux-DM_Multipath-6-en-US-1-18.

[comment] as version number change consider using 


Comment 8 releng-rhel@redhat.com 2010-11-11 15:27:40 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.