All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Soltys <soltys@ziu.info>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev lvm permisions
Date: Mon, 15 Dec 2008 16:13:22 +0000	[thread overview]
Message-ID: <49468222.90403@ziu.info> (raw)
In-Reply-To: <1229336451.19633.4.camel@linux-pqqd.site>

Geert Geurts wrote:
> 
> 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!
> 

As I corrected myself earlier - if you really need udev to do so, you 
need rules file that will create the names as lvm would do.

Or you can extend a bit the above rules and make udev create that 
particular device with the name you want, e.g.

ENV{DM_UUID}="<uuid>", NAME:="<something>" GROUP="users", MODE="0660"

This guarantees that no rule later will alter the name. It also assumes 
you're using udev>\x131 and nothing earlier did NAME:= (with 130 and 
earlier, any earlier NAME= or NAME:= assignment was final).
Then - just use /dev/<something> to access your volume however you need.

Or ... you can just add simple chown / chmod somewhere after lvm is 
activated (not very flexible, but definitely simple).


Anyway - I needed similar thing at one of my machines, where squid cache 
uses coss storage. Squid runs unprivileged, but had to access coss 
device directly. I use rules mimicking lvm/dmsetup behaviour though, so 
simple NAME= test was enough in my case. If you're curious - 
http://marc.info/?l=linux-hotplug&m\x122165542423023&q=p3

With that, I have
ACTION="add|change", SUBSYSTEM="block", NAME="mapper/vg0-coss", \
OWNER="squid", GROUP="squid"

Good luck

  parent reply	other threads:[~2008-12-15 16:13 UTC|newest]

Thread overview: 28+ 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
2008-12-15 15:47 ` Kay Sievers
2008-12-15 15:55 ` Scott James Remnant
2008-12-15 16:13 ` Michal Soltys [this message]
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:37   ` Alasdair G Kergon
2008-12-15 19:51 ` [lvm-devel] " Alasdair G Kergon
2008-12-15 19:51   ` Alasdair G Kergon
2008-12-15 20:14 ` David Zeuthen
2008-12-15 20:14   ` David Zeuthen
2008-12-15 20:29 ` Alasdair G Kergon
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=49468222.90403@ziu.info \
    --to=soltys@ziu.info \
    --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 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.