From: Alasdair G Kergon <agk@redhat.com>
To: "Linda A. Walsh" <lvm@tlinx.org>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Bug! lvs shouldn't need 'root' access
Date: Sun, 10 Jul 2011 23:08:15 +0100 [thread overview]
Message-ID: <20110710220815.GB7857@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <4E19E3FD.9000805@tlinx.org>
On Sun, Jul 10, 2011 at 10:40:13AM -0700, Linda A. Walsh wrote:
> I could write to the darn things!, but all I NEED is read (hmmm
I thought so too when we first began work on LVM, but - surprising
to me - there's been hardly any demand expressed for this feature.
The proposed method of handling this was to accept dm ioctls on
the actual devices themselves controlled by normal ioctl permissions.
Currently, you need CAP_SYS_ADMIN (and access to /dev/mapper/control).
Alasdair
next prev parent reply other threads:[~2011-07-10 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 17:40 [linux-lvm] Bug! lvs shouldn't need 'root' access Linda A. Walsh
2011-07-10 22:08 ` Alasdair G Kergon [this message]
2011-07-11 1:24 ` Linda A. Walsh
2011-07-11 2:24 ` Alasdair G Kergon
2011-07-11 2:31 ` Linda A. Walsh
2011-07-11 2:53 ` Alasdair G Kergon
2011-07-12 10:58 ` Linda A. Walsh
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=20110710220815.GB7857@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=lvm@tlinx.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;
as well as URLs for NNTP newsgroup(s).