Bug 68378

Summary:	confusing LVM text in release notes
Product:	[Retired] Red Hat Public Beta	Reporter:	James Manning <jmm>
Component:	anaconda-help	Assignee:	John Ha <jha>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	limbo	CC:	adstrong
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-07-12 05:08:57 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:
Bug Depends On:
Bug Blocks:	67217

Description James Manning 2002-07-09 16:36:46 UTC

"If you have preexisting VG with a particular name, you can create a new one
with that name.  The name can be anything, so be descriptive"

1) saying the name can be anything is just asking for bad characters and AFAICT
the name-checking validation stuff isn't working yet

2) bad grammar - probably "If you have *a* preexisting VG with a particular name"

3) doesn't make any sense - it's saying you can have 2 VG's with the same name
which is not true

Comment 1 James Manning 2002-07-09 16:39:11 UTC

ugh - the release notes are half-way to ZeroWing - more entries like "(this
partially the point of LVM)" - who's doing these docs? Tonto? sheesh :)

Comment 2 John Ha 2002-07-19 16:44:06 UTC

Thank you for brining this to our attention. We have rewritten the LVM section
and the changes will be made available by the next release. 

FYI, we have completely removed the first passage you mentioned as it was too
confusing and seemed out of place, especially considering that LVM configuration
in the installer is a new feature and that most users probably have not used LVM
before. The second passage you mentioned has been removed as well.

Thanks again for pointing out these confusing sections of the release notes.

Comment 3 Michael Fulbright 2002-12-20 17:38:25 UTC

Time tracking values updated