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

[Andreas Jellinghaus <aj@dungeon.inka.de>]

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.

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.

Now, I'd love if the kernel would keep the permissions that devfs
has. you don't. nobody else wrote something about it? but that issue
isn't that important.

I'd like to see a different namespace. 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.

how do you call that distinction cdrom/disc? type? class? I don't now.
I was under the impression, that this should be part of the path to
the dev file, i.e. cdroms should be in a cdrom/ directory and 
discs in a disc/ directory. would that be a major change?

the alternative would be an additional attribute to the kobject
with that information. 

I'm no kernel hacker, I can bareley understand some parts of the code
and do trivial changes. But I will try to learn more and maybe be
of some help.

Andreas