Bug 746095

Summary:	Section 32.4 - Kickstart options for <part> keyword is confusing/incorreect.
Product:	Red Hat Enterprise Linux 6	Reporter:	Kwan Lowe <kwan>
Component:	doc-Installation_Guide	Assignee:	Jack Reed <jreed>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ecs-bugs
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	jreed, jskeoch, pbokoc
Target Milestone:	rc	Keywords:	Documentation
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-25 23:33:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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.