From: jw schultz <jw@pegasys.ws>
To: linux-kernel@vger.kernel.org
Subject: Re: [cgl_discussion] RE: ANNOUNCE: User-space System Device Enumation (uSDE)
Date: Wed, 29 Oct 2003 17:01:26 -0800 [thread overview]
Message-ID: <20031030010126.GF12626@pegasys.ws> (raw)
In-Reply-To: <20031029190715.GA4241@kroah.com>
On Wed, Oct 29, 2003 at 11:07:16AM -0800, Greg KH wrote:
> On Wed, Oct 29, 2003 at 05:20:01PM +0100, Eric.Chacron@alcatel.fr wrote:
> >
> >
> > >From a pure technical point of view and from presentations made by the
> > authors of u*** perspective
> > i think uSDE could add some interresting features like a customizable
> > naming policy.
>
> udev doesn't provide such a feature right now?
>
> > For instance: geographical addressing to identify devices using rack,
> > subrack, slot numbers seems possible.
>
> Sure, udev can do that today, if you have a way of identifying devices
> in such a manner.
.From a distance this udev vs uSDE remind me of dm vs evms.
Based on the rhetoric udev is oriented toward implementing
policy and uSDE, articulating policy. It seems to me that
the code that should be run on device add and remove ought
to be implementation oriented not policy oriented. When
policy articulation is wanted it belongs in the user
interface. This could be a set of files to build the final
config file or a library and user interface. A bit like
using EVMS to manage dm.
Just my $0.02 in case distance lends perspective.
I also wonder how one is supposed to pronounce uSDE,
you-zdee, us-dee, us-day?
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember Cernan and Schmitt
next prev parent reply other threads:[~2003-10-30 1:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 16:20 [cgl_discussion] RE: ANNOUNCE: User-space System Device Enumation (uSDE) Eric.Chacron
2003-10-29 19:07 ` Greg KH
2003-10-30 1:01 ` jw schultz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-29 5:12 Guo, Min
2003-10-29 19:04 ` Greg KH
2003-10-30 0:37 ` [cgl_discussion] " Rusty Lynch
2003-10-30 0:57 ` 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=20031030010126.GF12626@pegasys.ws \
--to=jw@pegasys.ws \
--cc=linux-kernel@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).