Bug 1369436

Summary: losetup man page incorrect syntax for Setup loop device
Product: Red Hat Enterprise Linux 7 Reporter: Thom Carlin <tcarlin>
Component: util-linuxAssignee: Karel Zak <kzak>
Status: CLOSED ERRATA QA Contact: Radka Brychtova <rskvaril>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.2CC: bblaskov, nforro, rskvaril
Target Milestone: rcKeywords: ManPageChange
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: util-linux-2.23.2-36.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 21:41:11 UTC Type: Bug
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: 1380361    

Description Thom Carlin 2016-08-23 12:20:33 UTC
Description of problem:

"Setup loop device" section missing space between -f and --show

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

RHEL 7.2

How reproducible:

100%

Steps to Reproduce:
1. man losetup
2.
3.

Actual results:

            losetup [-o offset] [--sizelimit size]
                    [-p pfd] [-rP] {-f[--show]|loopdev} file


Expected results:

            losetup [-o offset] [--sizelimit size]
                    [-p pfd] [-rP] {-f [--show]|loopdev} file

Additional info:

Comment 2 Nikola Forró 2016-08-23 15:42:46 UTC
Thom, losetup.8 man page isn't part of man-pages package. I'm going to reassign this bug to util-linux.

Comment 3 Karel Zak 2016-08-29 11:28:51 UTC
This is really cosmetic issue, should be fixed with something more important in 7.4. The current upstream uses:

losetup [-o offset] [--sizelimit size]
        [-Pr] [--show] -f|loopdev file

Comment 8 errata-xmlrpc 2017-08-01 21:41:11 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2186