From: Rusty Lynch <rusty@linux.co.intel.com>
To: Greg KH <greg@kroah.com>
Cc: "Guo, Min" <min.guo@intel.com>,
linux-raid@vger.kernel.org,
linux-hotplug-devel@lists.sourceforge.net,
Lars Marowsky-Bree <lmb@suse.de>,
"Ling, Xiaofeng" <xiaofeng.ling@intel.com>,
Mark Bellon <mbellon@mvista.com>,
linux-kernel@vger.kernel.org, cgl_discussion@osdl.org,
Steven Dake <sdake@mvista.com>
Subject: Re: [cgl_discussion] Re: ANNOUNCE: User-space System Device Enumation (uSDE)
Date: Wed, 29 Oct 2003 16:37:20 -0800 [thread overview]
Message-ID: <20031030003720.GA6000@penguin.co.intel.com> (raw)
In-Reply-To: <20031029190421.GA4173@kroah.com>
On Wed, Oct 29, 2003 at 11:04:21AM -0800, Greg KH wrote:
<huge snip>
> In the interest of full disclosure, Min is one of the SDE authors, and I
> am one of the udev authors.
man... I saw this thread and thought there is no way in hell I am jumping in
this bloody mess. oh well...
...and I told Min to help out on usde.
>
> Min, maybe you can answer why Intel has spent effort on this project
> instead of offering to help udev, which has been public for a long time
> now?
>
I have never believed that any one implementation of (in CGL speak) "persistent
device naming" would be palatable by everyone, and have no problem in donating
some resources toward udev.
In the past we experimented with udev, and even did a little work on
sysfsutils (which I though udev was using, but looking at udev-005 I still
see the libsysfs directory.)
I see the the TODO list in udev-005. Are all these items wide open, or have
people already spoken for some parts? Maybe you have a couple of items you
consider higher priority?
--rustyl
next prev parent reply other threads:[~2003-10-30 0:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 5:12 ANNOUNCE: User-space System Device Enumation (uSDE) Guo, Min
2003-10-29 16:10 ` Steven Dake
2003-10-29 19:04 ` Greg KH
2003-10-30 0:37 ` Rusty Lynch [this message]
2003-10-30 0:57 ` [cgl_discussion] " Greg KH
2003-10-29 16:20 [cgl_discussion] " Eric.Chacron
2003-10-29 19:07 ` Greg KH
2003-10-30 1:01 ` jw schultz
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=20031030003720.GA6000@penguin.co.intel.com \
--to=rusty@linux.co.intel.com \
--cc=cgl_discussion@osdl.org \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=lmb@suse.de \
--cc=mbellon@mvista.com \
--cc=min.guo@intel.com \
--cc=sdake@mvista.com \
--cc=xiaofeng.ling@intel.com \
/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).