linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* DM & udev
@ 2004-02-05  0:20 christophe varoqui
  2004-02-05 17:24 ` Greg KH
  2004-02-06  2:09 ` [dm-devel] " Kevin Corry
  0 siblings, 2 replies; 3+ messages in thread
From: christophe varoqui @ 2004-02-05  0:20 UTC (permalink / raw)
  To: linux-hotplug

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.

regards,
cvaroqui


-------------------------------------------------------
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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: DM & udev
  2004-02-05  0:20 DM & udev christophe varoqui
@ 2004-02-05 17:24 ` Greg KH
  2004-02-06  2:09 ` [dm-devel] " Kevin Corry
  1 sibling, 0 replies; 3+ messages in thread
From: Greg KH @ 2004-02-05 17:24 UTC (permalink / raw)
  To: linux-hotplug

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [dm-devel] Re: DM & udev
  2004-02-05  0:20 DM & udev christophe varoqui
  2004-02-05 17:24 ` Greg KH
@ 2004-02-06  2:09 ` Kevin Corry
  1 sibling, 0 replies; 3+ messages in thread
From: Kevin Corry @ 2004-02-06  2:09 UTC (permalink / raw)
  To: linux-hotplug

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-02-06  2:09 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-02-05  0:20 DM & udev christophe varoqui
2004-02-05 17:24 ` Greg KH
2004-02-06  2:09 ` [dm-devel] " Kevin Corry

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).