From: Geert Geurts <begeert@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev lvm permisions
Date: Mon, 15 Dec 2008 15:24:04 +0000 [thread overview]
Message-ID: <1229354644.22135.8.camel@linux-pqqd.site> (raw)
In-Reply-To: <1229336451.19633.4.camel@linux-pqqd.site>
Hello kay,
Thanks for your reply!
Indeed it's about a logical volume I want to mount as a normal user.
I've already had discussion with Michal Soltys,
he sugested to create a rule according to the following:
ACTION!="add|change", GOTO="dm_end"
KERNEL!="dm*", GOTO="dm_end"
PROGRAM="/sbin/dmsetup info -c --noheadings -o uuid -j%M -m%m",
ENV{DM_UUID}="%c"
ENV{DM_UUID}="LVM-N28qi20mqjyPR150TYivmJzvkn8zzpi2VEhSFspDTiAxn2GLFC7xJ8Lfh12dmGH0", GROUP="users", MODEf0
LABEL="dm_end"
I've created this rule but it applies to the kernel device... /dev/dm-*.
What I need is a rule that changes the ownership
of /dev/mapper/HomeVolume.
Thats where I stand now,
so any suggestions are welcome!
Greetings,
Geert
On Mon, 2008-12-15 at 15:59 +0100, Kay Sievers wrote:
> On Mon, Dec 15, 2008 at 11:20, Geert Geurts <begeert@gmail.com> wrote:
> > I have created a encrypted lvm home volume for placing personal files,
> > and using them on different distributions.
> > I'm using OpenSuse 11 and Ubuntu 8.10 both distributions are configured
> > to decrypt the HomeVolume on login using pam_mount. The problem is that
> > the permissions to the HomeVolume are not set correctly by Suse, so the
> > volume cannot be decrypted and cannot be mounted.
> > How can I create a udev rule that applies only to one LVM volume?
>
> What kind of permissions? The ownership of the block device? Do you
> need to mount it as a user, not as root?
>
> Kay
next prev parent reply other threads:[~2008-12-15 15:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 10:20 udev lvm permisions Geert Geurts
2008-12-15 11:35 ` Michal Soltys
2008-12-15 14:23 ` Michal Soltys
2008-12-15 14:59 ` Kay Sievers
2008-12-15 15:24 ` Geert Geurts [this message]
2008-12-15 15:47 ` Kay Sievers
2008-12-15 15:55 ` Scott James Remnant
2008-12-15 16:13 ` Michal Soltys
2008-12-15 17:02 ` David Zeuthen
2008-12-15 17:06 ` Scott James Remnant
2008-12-15 17:12 ` David Zeuthen
2008-12-15 17:14 ` Kay Sievers
2008-12-15 17:18 ` Scott James Remnant
2008-12-15 17:19 ` Kay Sievers
2008-12-15 17:21 ` Geert Geurts
2008-12-15 17:37 ` Kay Sievers
2008-12-15 17:59 ` Scott James Remnant
2008-12-15 18:19 ` Kay Sievers
2008-12-15 18:21 ` Scott James Remnant
2008-12-15 18:38 ` Kay Sievers
2008-12-15 19:37 ` Alasdair G Kergon
2008-12-15 19:51 ` [lvm-devel] " Alasdair G Kergon
2008-12-15 20:14 ` David Zeuthen
2008-12-15 20:29 ` Alasdair G Kergon
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=1229354644.22135.8.camel@linux-pqqd.site \
--to=begeert@gmail.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).