From: Karel Zak <kzak@redhat.com>
To: kalle <kalle@projektwerkstatt.de>
Cc: util-linux@vger.kernel.org
Subject: Re: man lsblk
Date: Wed, 22 Nov 2017 13:00:28 +0100 [thread overview]
Message-ID: <20171122120028.lozaoz4fifrzvzjj@ws.net.home> (raw)
In-Reply-To: <bc06a7b2-87f3-50af-4e51-f9f3166186d4@projektwerkstatt.de>
On Tue, Nov 21, 2017 at 11:44:17PM +0100, kalle wrote:
> hello,
> here some critics:
> -I had problems with reading the label through `lsblk', when not using
> privileges. And the related man-page doesn't mention privilege matters.
> For what is mentioned (in the `Notes'), that /sys/dev/block has to be
> readable, my systems seems to be ok (read and write rights granted for
> `others') -> I assume that it is a question of privileges, which should
> be better documented
Frankly, I'm not sure if this is the right place to discuss end-user
issues. It would be better to use distro specific mailing list or bug
tracker. For example I have no clue if you have lsblk with or without
udev support, used versions, etc. etc.
> -proposition: put the options of `lsblk(8)' explicitly in the man-file
> instead than only in `lsblk --help'
> -`lsblk -m -o LABELs'shows only LABELs, but why? While `lsblk -o LABEL
> -m' shows both. I think the options should be commutative...
I cannot reproduce this problem with 2.30.2 and the current upstream
tree.
> -after unmounting a device `lsblk' doesn't list it anymore
Hmm... lsblk list block device, mount/umount affects only MOUNTPOINT
column.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2017-11-22 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 22:44 man lsblk kalle
2017-11-22 12:00 ` Karel Zak [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171122120028.lozaoz4fifrzvzjj@ws.net.home \
--to=kzak@redhat.com \
--cc=kalle@projektwerkstatt.de \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.