On Tue, 2003-10-28 at 04:00, Lars Marowsky-Bree wrote:

On 2003-10-27T14:14:18,
   Mark Bellon [off-list ref] said:

quoted

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
;-)

There are several distinct approaches which have been enumerated in
other mails.

Since this point has not been addressed, I'd like to focus on the major
difference in philosophy.

SDE places all policy in the hands of the policy developer in a seperate
policy program.  udev places the policies in the main processing loop of
the system, effectively implementing whatever policy is desired by the
udev maintainers.

Without seperating policies from the core executive of device naming
system, the core of udev suffers from the same issues as placing policy
in the kernel suffers.   Lack of maintainability, lack of user-defined
functionality, bloat, etc.

quoted

quoted

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.

No but this is definately a good idea.
Thanks!
-steve

Sincerely,
    Lars Marowsky-Brée [off-list ref]

-
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