From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Corry Date: Wed, 03 Dec 2003 14:31:26 +0000 Subject: Re: udev and EVMS Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Wednesday 03 December 2003 07:32, Marco d'Itri wrote: > Who is at fault? Both udev and EVMS are creating nodes in /dev. > > ----- Forwarded message from Martin Waitz ----- > > > I think dm manages its nodes by itself. > > hmm, i'm using evms and yes, it creates its nodes by itself. > but i get 'dm-[0-9]' files in udev, too > one for every logical volume (but without the correct name, just the > number) > > so perhaps one would have to suppress creation of these nodes? > > > ----- End forwarded message ----- I don't see why there should be a problem with EVMS and udev operating at the same time (although I haven't actually tried udev yet). EVMS has to be able to create it's device nodes in /dev/evms. The kernel has no knowledge of the names that EVMS gives to its volumes (which are the names given to the EVMS device nodes). Device-Mapper only creates dm-? entries, which doesn't give the user any clue as to which device-node corresponds to which volume. EVMS only ever creates nodes in /dev/evms/, and the kernel never creates a name for a block-device that would clash with these. So I'm curious why there would be a conflict between EVMS and udev. -- Kevin Corry kevcorry@us.ibm.com http://evms.sourceforge.net/ ------------------------------------------------------- This SF.net email is sponsored by OSDN's Audience Survey. Help shape OSDN's sites and tell us what you think. Take this five minute survey and you could win a $250 Gift Certificate. http://www.wrgsurveys.com/2003/osdntech03.php?site=8 _______________________________________________ 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