Bug 1031641 - findmnt should handle better trailing "/" in /proc/mounts entries
Summary: findmnt should handle better trailing "/" in /proc/mounts entries
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: util-linux-ng
Version: 6.5
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Karel Zak
QA Contact: Branislav Blaškovič
URL:
Whiteboard:
Depends On:
Blocks: 1027410
TreeView+ depends on / blocked
 
Reported: 2013-11-18 13:02 UTC by Fabio Massimo Di Nitto
Modified: 2014-10-14 07:34 UTC (History)
3 users (show)

Fixed In Version: util-linux-ng-2.17.2-12.16.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-14 07:34:46 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1545 0 normal SHIPPED_LIVE util-linux-ng bug fix and enhancement update 2014-10-14 01:21:29 UTC

Description Fabio Massimo Di Nitto 2013-11-18 13:02:06 UTC 
Description of problem:

Looking for example at bug#1031636, where filesystems can potentially add a trailing slash in the device section of /proc/mounts

192.168.1.1:/mnt/ ....

it would very useful if findmnt could automatically handle it when issuing commands similar to:

findmnt -o TARGET --noheadings 192.168.1.1:/mnt

and match the device, since effectively there can´t be both devices at the same time.

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

util-linux-ng-2.17.2-12.14.el6.x86_64
Comment 1 Karel Zak 2013-11-19 10:25:13 UTC 
It's already implemented for upstream, Fedora and RHEL7. It should be pretty simple to backport the function to RHEL6.
Comment 7 errata-xmlrpc 2014-10-14 07:34:46 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.

http://rhn.redhat.com/errata/RHBA-2014-1545.html
Note You need to log in before you can comment on or make changes to this bug.