Bug 746095 - Section 32.4 - Kickstart options for <part> keyword is confusing/incorreect.
Summary: Section 32.4 - Kickstart options for <part> keyword is confusing/incorreect.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Installation_Guide
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Jack Reed
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-13 21:05 UTC by Kwan Lowe
Modified: 2013-06-17 05:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-25 23:33:06 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Kwan Lowe 2011-10-13 21:05:51 UTC 
Description of problem:
BNF for part keyword is incorrect:
<mntpointmultipath --name= --device= --rule=> — The <mntpoint> is where the
partition is mounted and must be of one of the following forms:

In the above section, <mntpoint> is indicated but not listed. 
mntpointmultipath is not referenced elsewhere.
--name=  does not have correct notation, etc..


Version-Release number of selected component (if applicable):
Latest published document as of 10.14.2011

How reproducible:
N/A

Steps to Reproduce:
1. 
2.
3.
  
Actual results:


Expected results:
Proper BNF notation for part keyword.. E.g.
part [--size=<size_in_blocks>] [--type=<foo|bar>] 
etc..



Additional info:
Comment 2 Jack Reed 2012-03-06 03:28:21 UTC 
Due to time constraints, pushing to 6.4 because this is a fairly meticulous formatting issue.
Comment 3 Jack Reed 2012-10-19 03:09:07 UTC 
Thanks for reporting this. 

I've tidied up the layout and placed the example syntax in a proper breakout. I've corrected 'mntpointmultipath' to just 'mntpoint' and the example syntax is now as follows:

part|partition <mntpoint> --name=<name> --device=<device> --rule=<rule> <options>
Comment 6 Jack Reed 2013-02-25 23:33:06 UTC 
This bug has been verified and implemented for 6.4, so I am changing the status to CLOSED CURRENT RELEASE.
Note You need to log in before you can comment on or make changes to this bug.