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

[John Cherry <cherry@osdl.org>]

> > The requirements were collected from the OSDL CGL requirements 
> > specification version 1.0 and 1.1 ratified September 2002. They come 
> > from extensive discussions with the OSDL members as part of the 
> > definition of these requirements, expounding on them:
> 
> Wait, all the Carrier Grade Linux Requirement Definition Version 2.0 say
> about "Persistent Device Naming" is the following:
> 
> 	OSDL CGL specifies that carrier grade Linux shall provide
> 	functionality such that a device's identity shall be maintained
> 	when it is removed and reinstalled even if it is plugged into a
> 	different bus, slot, or adapter.  "Device identity" is the name
> 	of the device presented to user space, and this identity is
> 	assigned based on policies set by the administrator, e.g., based
> 	on location or hardware identification information.

Thanks for point out the actual CGL requirement, Greg. 


> > The two packages take philosophically different approaches and arrive 
> > with (largely) overlapping and some non-overlapping capabilities - after 
> > all they are both trying to do "the same thing". The uSDE has strengths 
> > and weaknesses just as udev or any program does. It is certainly 
> > possible to discuss changes (and make patches) to udev to incorporate 
> > the key issues addressed in the uSDE implementation.
> 
> Besides the refusal to handle network devices, I don't see any thing
> that udev is lacking that uSDE has.  But I'm not too familar with uSDE,
> being that it has only been released for a few days now.  If you could
> point out anything that udev is lacking, I would be glad to help solve
> that.
> 

The Carrier Grade Linux specification has never dictated an
implementation.  In fact, both udev and uSDE are listed as potential
implementations.

As Lars stated in an earlier email, "Competition is good, but only if
they explore distinct approaches".  It is a shame that much effort has
been duplicated here on similar approaches.  I'm not fully aware of the
history behind the divergence, but it makes sense to enumerate NOW what
is lacking in udev from a uSDE perspective.  One objective of the
carrier grade initiative is to prevent duplicate effort.  Now that we
have two implementations, let's get the issues/differences on the table
and cooperatively move to convergence.

John



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  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