All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Rajnoha <prajnoha@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Udev integration for device-mapper and its subsystems.
Date: Wed, 29 Apr 2009 21:44:59 +0000	[thread overview]
Message-ID: <49F8CA5B.3000901@redhat.com> (raw)
In-Reply-To: <49F5DC36.9080309@redhat.com>

On 04/29/2009 10:46 PM, Kay Sievers wrote:
>> TEST="dm", ENV{DM_NAME}="$attr{dm/name}", ENV{DM_UUID}="$attr{dm/uuid}"
>> TEST!="dm", IMPORT{program}="/sbin/dmsetup info -j %M -m %m -c --nameprefixes --noheadings --rows -o name,uuid"
> 
> Wasn't there something that added the DM_* variables to the kernel
> directly? I remember seing something a while back. If that is still
> planned or possible, maybe you can just do thes both rules only if the
> values are not set?
> 
> ENV{DM_NAME}="", ENV{DM_NAME}="$attr{dm/name}", ...
> ENV{DM_NAME}="", IMPORT{program}= ...

I think these are multipath uevents only. But uevents for plain
DM devices don't have these vars set. But yes, we can save a little
time in that particular situation.

>> ENV{DM_NAME}="?*", NAME="$kernel", SYMLINK+="mapper/$env{DM_NAME}"
> 
> NAME="$kernel" is the default, it's not needed.

..ok

> Yeah, looks great.

Thanks! :)

Peter

      parent reply	other threads:[~2009-04-29 21:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 16:24 Udev integration for device-mapper and its subsystems Peter Rajnoha
2009-04-28 17:41 ` Kay Sievers
2009-04-28 18:45 ` Alasdair G Kergon
2009-04-28 19:24 ` Kay Sievers
2009-04-28 21:16 ` Milan Broz
2009-04-28 21:25 ` Kay Sievers
2009-04-29  0:28 ` Alasdair G Kergon
2009-04-29  1:16 ` Kay Sievers
2009-04-29  2:45 ` Alasdair G Kergon
2009-04-29 10:05 ` Kay Sievers
2009-04-29 11:52 ` Milan Broz
2009-04-29 12:41 ` Karel Zak
2009-04-29 12:55 ` Kay Sievers
2009-04-29 12:59 ` Hannes Reinecke
2009-04-29 13:45 ` Kay Sievers
2009-04-29 20:11 ` Peter Rajnoha
2009-04-29 20:46 ` Kay Sievers
2009-04-29 21:44 ` Peter Rajnoha [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=49F8CA5B.3000901@redhat.com \
    --to=prajnoha@redhat.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 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.