From: Kevin Corry <kevcorry@us.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and EVMS
Date: Wed, 03 Dec 2003 14:31:26 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107046199607429@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107045977504751@msgid-missing>
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
prev parent reply other threads:[~2003-12-03 14:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 13:32 udev and EVMS Marco d'Itri
2003-12-03 14:31 ` 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=marc-linux-hotplug-107046199607429@msgid-missing \
--to=kevcorry@us.ibm.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.