linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Bellon <mbellon@mvista.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: ANNOUNCE: User-space System Device Enumeration (uSDE)
Date: Mon, 27 Oct 2003 23:09:26 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-106729663930306@msgid-missing> (raw)

>
>
>How does uSDE relate to udev? You do not mention it in your email, though it claims to implement similar, if not identical functionality. Is it related? Is it built on top of it?
>
The uSDE is not built on top of udev.

The uSDE and udev are similar in some respects. They both create device 
nodes. There is a lot more to handling devices than managing device nodes.

Some differences between uSDE and udev that come to mind as I type (a 
good deal of this is part of the INTRO in the uSDE tarball):

Devices are classified and an explicit, ordered list of policies are 
invoked on behalf of the devices based on that classification.

Policies are implemented as open plug-ins that have complete control 
(e.g. naming, configuration, special needs) over a device.

Multiple policies can be executed concurrently; they can be independent 
or cooperative.

All device types are embraced - ethernet, disks, cdroms, floppies, MD, 
LVM and so on. Policies can analyze data and handle complex situations 
such as ethernet interface anchoring, multiported disk handling and 
automatic multipath device management.

The concept of service agents who provide critical information to the 
enumeration framework allowing policies to handle extremely diverse 
hardware situations such as multiple chassis and geographical addressing.

The uSDE sample policies implement basic device replacement and 
relocation strategies, something that the community has been asking 
about for some time.

If you want to learn more about that differences, download the tarball 
and try it out...

The uSDE was built in response to a set of telco and embedded community 
requirements. We found it difficult to express our ideas. Everyone 
wanted to see code and documentation. Here is the code and the initial 
documentation. This is a starting point...

>If not, are you planning on merging your efforts with udev in the future?
>
It is to everyone's advantage to converge on an implementation of 
enumeration that meets all of the requirements.

>Are you using the libsysfs library for accessing sysfs data? If not, I 
>highly recommend it.
>
The uSDE is not currently using the libsysfs library. The project will 
look into this in the near future.

Patches gladly accepted. :)

>I would also recommend sending email to the linux-hotplug list, as most of 
>the hotplug-related applications are discussed and developed via that 
>list.
>
>
>	Pat
>
Thanks, I'll copy them.

mark




-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
_______________________________________________
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

             reply	other threads:[~2003-10-27 23:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27 23:09 Mark Bellon [this message]
2003-10-27 23:39 ` ANNOUNCE: User-space System Device Enumeration (uSDE) Greg KH
2003-10-28 17:16 ` Patrick Mochel
2003-10-28 17:29 ` Lars Marowsky-Bree
2003-10-28 17:47 ` Mark Bellon
2003-10-28 18:12 ` Mark Bellon
2003-10-28 18:17 ` Greg KH
2003-10-28 18:45 ` Chris Friesen
2003-10-28 18:48 ` Greg KH
2003-10-28 19:40 ` John Cherry
2003-10-28 19:53 ` Greg KH

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-106729663930306@msgid-missing \
    --to=mbellon@mvista.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 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).