Re: ANNOUNCE: User-space System Device Enumeration (uSDE)

[Mark Bellon]

> 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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/