From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: DM & udev
Date: Thu, 05 Feb 2004 17:24:01 +0000 [thread overview]
Message-ID: <20040205172401.GG12546@kroah.com> (raw)
In-Reply-To: <40218C4B.4010709@free.fr>
On Thu, Feb 05, 2004 at 01:20:27AM +0100, christophe varoqui wrote:
> Hello,
>
> what's the rationale behind the enum-style naming of DM in /sys/block ?
> a nasty side effect is that /udev names are not the DM name like devfs
> did (/dev/mapper/vg01-vol01), but those dm-0, dm-1, ...
>
> One might insert yet another rule in udev to translate, but I wondered
> if there was a real reason for the dm-* names.
>
> Either way, I can get rid of the mknod code in the multipath tool, and
> let udev react to /sys/blocl/$any-dm-name spawning. Greg if you confirm
> that assertion, I'll submit this patch for the next udev release.
udev should be able to handle dm-* names just fine as long as there is a
'dev' file in the directory for them (which I'm pretty sure there is...)
thanks,
greg k-h
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-02-05 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 0:20 DM & udev christophe varoqui
2004-02-05 17:24 ` Greg KH [this message]
2004-02-06 2:09 ` [dm-devel] " Kevin Corry
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=20040205172401.GG12546@kroah.com \
--to=greg@kroah.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).