devfs
[Top] [All Lists]

Re: module loading

To: Borzenkov Andrey <Andrey.Borzenkov@xxxxxxxxxxx>, devfs@xxxxxxxxxxx
Subject: Re: module loading
From: Russell Coker <russell@xxxxxxxxxxxx>
Date: Thu, 27 Mar 2003 12:19:34 +0100
In-reply-to: <6134254DE87BD411908B00A0C99B044F03A0B68C@mowd019a.mow.siemens.ru>
References: <6134254DE87BD411908B00A0C99B044F03A0B68C@mowd019a.mow.siemens.ru>
Reply-to: Russell Coker <russell@xxxxxxxxxxxx>
Sender: devfs-bounce@xxxxxxxxxxx
User-agent: KMail/1.5.1
On Thu, 27 Mar 2003 07:07, Borzenkov Andrey wrote:
> > Would it be possible to have the kernel execute modprobe when a non-
> > existant
> > device node is accessed?
> >
> > IE If an application attempts to access /dev/ppp could the kernel run
> > "modprobe /dev/ppp" directly (not through devfsd)?
>
> Theoretically, yes. Doing this means that either every file system must
> support it in its ->lookup method or you need special file system type for
> /dev. The latter exists and is called devfs :) The former may be

I only want to use devfs.

The problem is that currently modprobe is only run by devfsd in the case of a 
lookup of a non-existant device, while the kernel runs modprobe in the case 
of a device node existing but there being no driver to match.

I would like to have the kernel run modprobe in both instances to remove the 
need for devfsd on small systems.

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page


<Prev in Thread] Current Thread [Next in Thread>