On Wed, May 11, 2005 at 07:36:54PM +0200, Per Liden wrote:
> On Tue, 10 May 2005, Greg KH wrote:
>
> > On Wed, May 11, 2005 at 01:56:01AM +0200, Per Liden wrote:
> > > On Tue, 10 May 2005, Greg KH wrote:
> > >
> > > > On Wed, May 11, 2005 at 12:17:12AM +0200, Per Liden wrote:
> > > > > I'd like to get a better understanding of that as well. Why invent a
> > > > > second on demand module loader when we have kmod? The current approach
> > > > > feels like a step back to something very similar to the old kerneld.
> > > >
> > > > kmod is not used at all if you are running udev on your system.
> > >
> > > Since when does udev load modules for you?
> >
> > It does not. That was my point :)
>
> Sorry, but I still don't get your point. Whether kmod is used or not is
> unrelated to the use of udev.
I was trying to point out that if you use udev, kmod is not used at all
to autoload modules when you try to open a device file for a driver that
is not present (as if the module isn't loaded, then the device file
would not be present to try to open.)
But I forgot about the filesystem stuff...
Hope this clears things up.
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
