From: Greg KH <greg@kroah.com>
To: Andreas Jellinghaus <aj@dungeon.inka.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ANNOUNCE: User-space System Device Enumation (uSDE)
Date: Wed, 29 Oct 2003 14:43:13 -0800 [thread overview]
Message-ID: <20031029224313.GA1407@kroah.com> (raw)
In-Reply-To: <1067465573.28173.33.camel@simulacron>
On Wed, Oct 29, 2003 at 11:12:53PM +0100, Andreas Jellinghaus wrote:
> Hi Greg!
>
> On Wed, 2003-10-29 at 20:18, Greg KH wrote:
> > Sweet shell script, nice job.
> >
> > > So udev is 99% overhead?
> > To you, sure, it might be. Don't use it then, I'm not forcing anyone.
>
> Thats right! So I don't understand all those discussions why some people
> created an alternative to udev, as everyone is free to. All
> implementations seem to be quit young, and I enjoy many different
> approaches to solve these related problems. a bit of diversity or
> evolution and natural selection doesn't hurt.
I agree, evolution is good in this case. I'm just really curious as to
why Monta Vista and Intel decided that udev wasn't an approiate project
to work with, and decided to spend time and resources to develop an
alternative one. Just a bit frustrated, as udev really could have used
a few people working on it full time as SDE had.
But hey, that's all past, if those companies like to live with the NIH
symptom, I can't change that. And udev development will go on
regardless.
> But, all these different user space tools share one thing: the same
> kernel. the linux kernel has to work for all of us, and I even think
> it is very important to have many different user space tools at the
> current time, so everyone can voice their opinions and suggest how the
> kernel should be changed, so it will work for him, and preferable for
> all of us.
Agreed.
> I'd like to see a different namespace.
Different namespace where? In /sys? Or somewhere else?
> I need some info on block devices. currently there is no way to see if
> hdc is a cdrom or a disc in sysfs, so that should be added.
Not true at all. Just look at the device symlink, and the type file in
that directory. Shows it quite well for all of my scsi devices. Now it
looks like IDE needs to add that same type of file, but that's an IDE
issue. Actually IDE's sysfs code probably could use some good cleanups,
now that I look at it some more. Want to work on that?
thanks,
greg k-h
next prev parent reply other threads:[~2003-10-29 22:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F9D82F0.4000307@mvista.com>
[not found] ` <20031027210054.GR24286@marowsky-bree.de>
[not found] ` <3F9D8AAA.7010308@mvista.com>
2003-10-28 11:00 ` ANNOUNCE: User-space System Device Enumation (uSDE) Lars Marowsky-Bree
2003-10-28 18:12 ` Steven Dake
2003-10-28 22:44 ` Greg KH
2003-10-29 14:30 ` Andreas Jellinghaus
2003-10-29 17:20 ` Daniel Stekloff
2003-11-02 17:28 ` Andreas Jellinghaus
2003-11-03 23:29 ` Daniel Stekloff
2003-10-29 19:18 ` Greg KH
2003-10-29 22:12 ` Andreas Jellinghaus
2003-10-29 22:43 ` Greg KH [this message]
2003-10-29 5:12 Guo, Min
2003-10-29 16:10 ` Steven Dake
2003-10-29 19:04 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-10-31 0:45 David Dodge
2003-10-31 0:58 ` Greg KH
2003-10-31 2:29 ` Dave Dodge
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=20031029224313.GA1407@kroah.com \
--to=greg@kroah.com \
--cc=aj@dungeon.inka.de \
--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