Re: Hardware Abstraction Layer

[Greg KH <greg@kroah.com>]

On Sat, Sep 20, 2003 at 07:31:26PM +0000, Joerg Sommer wrote:
> begin  Greg KH <greg@kroah.com> wrote:
> > On Fri, Sep 19, 2003 at 08:11:14PM +0000, Joerg Sommer wrote:
> >> begin  Greg KH <greg@kroah.com> wrote:
> >> > Yes it will.  See my OLS paper from this year for lots more information
> >> > about it.
> >> 
> >> Nice to meet you here. :) I read this paper some time ago and one
> >> question stayed open: How does udev handle device requests? devfs has the
> >> nice feature to tell modprobe that a device is requested. But I don't
> >> found any similar in your paper. How gets udev informed that a program
> >> wants to open /dev/foobar?
> >
> > It doesn't :)
> >
> > If you _really_ need that kind of functionality, then you will have to
> > use devfs.
> 
> Why you removed this? IMO it is a very useful feature to only load a
> module if it is requested. Do you really think this is not needed?

I have not removed anything, this is just something that can not be done
from userspace alone (which is what udev is.)

And yes, I really do not think this is needed, as things have moved from
being a "load when we open the dev node" type system, to a "load when we
have found the hardware" type system.

But hey, if you really need this functionality, then use devfs.  I'm not
saying that udev can duplicate all of devfs's functionality, just the
majority of it (this is really the only exception that I can think of
right now.)

thanks,

greg k-h


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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