From: Kevin Corry <kevincorry@sbcglobal.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [dm-devel] Re: DM & udev
Date: Fri, 06 Feb 2004 02:09:04 +0000 [thread overview]
Message-ID: <200402052009.05291.kevincorry@sbcglobal.net> (raw)
In-Reply-To: <40218C4B.4010709@free.fr>
On Thursday 05 February 2004 11:24, Greg KH wrote:
> 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...)
The dm-* names are due to the separation between the DM core driver and the
ioctl interface. Only the ioctl interface knows the name of the device given
by the user. But only the core driver has access to the gendisk entry (and
hence the sysfs name). So the core assigns the gendisk a simple name based on
the minor number of the device.
And yes, there's a "dev" file in the dm-* directories, just as with all other
subdirs in /sys/block/.
--
Kevin Corry
kevincorry@sbcglobal.net
-------------------------------------------------------
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
prev parent reply other threads:[~2004-02-06 2:09 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
2004-02-06 2:09 ` Kevin Corry [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=200402052009.05291.kevincorry@sbcglobal.net \
--to=kevincorry@sbcglobal.net \
--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).