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: Tue, 28 Oct 2003 18:12:15 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-106736481606923@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106729663930306@msgid-missing>

Patrick Mochel wrote:

>>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...
>>    
>>
>
>I find it difficult to see your justification for designing a project from
>scratch instead of contributing your time, effort, and ideas to a pair of
>already existing, albeit immature, projects that do exactly the same
>thing.
>
>Please note that I'm not trying to incite yet another device naming flame
>war, but you have to understand how frustrating it is to see you guys make
>the same mistakes over and over, ad inifitum.
>
>Let's review. SDET was posted several months ago by the Montavista telco
>group as a 2.4 solution that was driven by customer requirements. So be
>it.
>
>In the last year, you (and/or your group) has posted several proposed
>device naming solutions; each of which were shot down because of
>over-design, misdirection, or simply tastelessness. Each time we
>encouraged you to align yourselves with the overall design goals or simply
>contribute to existing projects.
>
>Personal contact in Ottawa resulted the same message. IIRC, many if not
>all, of the atttending MV telco engineers even saw Greg's talk on udev.
>
>In the time since, you've designed and written a solution from scratch,
>without even trying to contribute to the udev effort. (And while, I might
>add, another MV engineer contributed several patches to in his free time
>to help package and productize it.)
>
>I fail to see your point in this project. AFAIC, you've wasted your time.
>It surely can't be customer requirements, as I highly doubt any customer
>solutions are based on a 2.6 kernel yet. You've completely duplicated the
>efforts of a project destined to become the de facto standard for the
>requirement you're trying to fulfill, for what gain?
>
>
>
>	Pat
>
>
>  
>
I can't respond to the emotion and ad hominum references in this 
message. The uSDE announcement is my first posting. I can't address any 
past dealings with MontaVista.

The uSDE ideas and implementation was started with the OSDL requirements 
in August of 2002.
This is the first time any form of it has been posted. From 
time-to-time, since the project started, ideas related to it have been 
floated with the community. The feedback was carefully listened to and 
utitized in the implementation that was just posted.

mark



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

  parent reply	other threads:[~2003-10-28 18:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27 23:09 ANNOUNCE: User-space System Device Enumeration (uSDE) Mark Bellon
2003-10-27 23:39 ` 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 [this message]
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-106736481606923@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).