From: Karel Zak <kzak@redhat.com>
To: helmut@hullen.de
Cc: util-linux@vger.kernel.org
Subject: Re: blkid tells different informations to user or root
Date: Mon, 7 Jan 2013 13:10:26 +0100 [thread overview]
Message-ID: <20130107121026.GE28963@x2.redhat.com> (raw)
In-Reply-To: <COGoGFiPCXB@helmut.hullen.de>
On Sat, Jan 05, 2013 at 12:20:00PM +0100, Helmut Hullen wrote:
> Running "blkid" as an underprivileged user apparently shows data (for
> sdb) which don't fit for the actually configuration.
Sure, if you have no permissions to revalidate the data...
> a) where's the bug for this different output?
It's expected behavior, this is reason why programs like mount(8)
have suid permissions.
Please, use lsblk(1) if you want see more reliable overview about
system block devices. It reads data from /sys and some details from
udevd DB.
> b) how can I create an actual "/run/blkid/blkid.tab"? Only via "rm"?
It should be unnecessary for privileged users.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
parent reply other threads:[~2013-01-07 12:10 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <COGoGFiPCXB@helmut.hullen.de>]
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=20130107121026.GE28963@x2.redhat.com \
--to=kzak@redhat.com \
--cc=helmut@hullen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox