Bug 145126 - Documentation unclear - Definitions are needed
Documentation unclear - Definitions are needed
Product: Red Hat Ready Certification Tests
Classification: Retired
Component: web site (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Yu Shao
Jeff Fearn
Depends On:
Blocks: 191699
  Show dependency treegraph
Reported: 2005-01-14 11:31 EST by Daniel W. Ottey
Modified: 2007-04-27 11:57 EDT (History)
0 users

See Also:
Fixed In Version: 1-07
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-04-27 11:57:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Daniel W. Ottey 2005-01-14 11:31:12 EST
Description of problem:
I think the iSpec documentation needs to be clearer in many of their
definitions.  Well, it would be nice if terms were defined somewhere.  Some of
the items we are not sure about (and can only assume our ES7000s have):

1) Multiple CPU Plans
2) Multiple Memory Planes
3) Multiple I/O Planes (drawers)

Under video controllers, we are unsure what the different words mean.  Please
4) Heads
5) Spanning
6) Mirroring
7) Console

And, what affect will selecting the above options have on the tests that are

As noted in a previous bug, “PC Card slots” should also be better clarified as
PCMCI slots.

Under disk storage devices, what does “Multiple Volumes” mean?

Providing these definitions would be greatly appreciated.  Thank you.

As examples:

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Rob Landry 2006-05-16 08:22:29 EDT
iSpec has been deprecated going forward; similar pages may be built into the
website going forward; thusly reassigning/filing against the website to ensure
comments/concerns are not lost
Comment 3 Rob Landry 2007-04-27 11:57:21 EDT
Documentation was re-written for RHEL5; please see 


for the updated documentation.  Problems with the new documentation should have
new bugs opened.

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