From: Lars Marowsky-Bree <lmb@suse.de>
To: Mark Bellon <mbellon@mvista.com>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ANNOUNCE: User-space System Device Enumation (uSDE)
Date: Tue, 28 Oct 2003 12:00:34 +0100 [thread overview]
Message-ID: <20031028110034.GG30725@marowsky-bree.de> (raw)
In-Reply-To: <3F9D8AAA.7010308@mvista.com>
On 2003-10-27T14:14:18,
Mark Bellon <mbellon@mvista.com> said:
> The uSDE and udev are simlar in some respects. The uSDE allows for
> complete control of the policy handling a device - not just its naming.
Well, so could udev in theory, and I had this plan to enhance it to do
so for the specific case of multipathing one day in the not too distant
future (ie, before q1/04).
In as far as I can see, udev and uSDE really do not have too different
goals. Competition is good, but only if they explore distinct approaches
;-)
> >How does this integrate with DM, md, EVMS, LVM...?
> As devices appear in sysfs the uSDE reacts to them via their hotplug
> events. The policy for each device handles any device issues including
> dealing with any device nodes. It is possible to track and maintain
> multiported devices and automatically provide multipath devices nodes
> for instance.
Yes, I know that, I was asking whether you had done any discussion with
the EVMS2 folks for example to have a policy plugin to interact with
EVMS2 accordingly and do the magic.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering \ ever tried. ever failed. no matter.
SUSE Labs | try again. fail again. fail better.
Research & Development, SUSE LINUX AG \ -- Samuel Beckett
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2003-10-28 11:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 20:41 ANNOUNCE: User-space System Device Enumation (uSDE) Mark Bellon
2003-10-27 21:00 ` Lars Marowsky-Bree
2003-10-27 21:14 ` Mark Bellon
2003-10-28 11:00 ` Lars Marowsky-Bree [this message]
2003-10-28 18:12 ` Steven Dake
2003-10-28 22:44 ` Greg KH
2003-10-27 23:15 ` Steven Dake
2003-10-27 23:19 ` Mark Bellon
-- strict thread matches above, loose matches on Subject: below --
2003-10-29 5:12 Guo, Min
2003-10-29 16:10 ` Steven Dake
2003-10-29 19:04 ` Greg KH
2003-10-31 0:45 David Dodge
2003-10-31 0:58 ` Greg KH
2003-10-31 2:29 ` Dave Dodge
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=20031028110034.GG30725@marowsky-bree.de \
--to=lmb@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mbellon@mvista.com \
/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).