Bug 518203
Summary: | No line breaks in the command sequence given in the example for 'exportfs' in Chapter 'Network File System (NFS)' | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Runa Bhattacharjee <runab> |
Component: | doc-Deployment_Guide | Assignee: | Douglas Silas <dhensley> |
Status: | CLOSED DUPLICATE | QA Contact: | Content Services Development <ecs-dev-list> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.3 | CC: | ankit |
Target Milestone: | rc | Keywords: | Documentation |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-08-19 14:22: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: | |
Embargoed: |
Description
Runa Bhattacharjee
2009-08-19 13:35:24 UTC
Thanks for the report. This is a duplicate of bug 453071; I'm working on solving that one now. The problem is actually that the computeroutput tag has been used in 837 places in the DocBook source, but that tag does not preserve line breaks in the source. That's what the DocBook manual means when it notes, in the description for computeroutput, that: "Note that computeroutput is not a verbatim environment, but an inline." Agreed that "verbatim environment" could have a secondary, more-explicit warning regarding line breaks... These will all need to be replaced with screen elements. *** This bug has been marked as a duplicate of bug 453071 *** |