From: Tomasz Torcz <zdzichu@irc.pl>
To: linux-hotplug@vger.kernel.org
Subject: Re: On demand modules loading with {tmp,ram}fs and udev
Date: Sat, 25 Oct 2003 01:09:32 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106704430028353@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106704029925575@msgid-missing>
On Fri, Oct 24, 2003 at 05:42:34PM -0700, Greg KH wrote:
> On Sat, Oct 25, 2003 at 02:00:18AM +0200, Tomasz Torcz wrote:
> > Hi,
> >
> > I was thinking about small addition to tmpfs. When mounted with 'dev'
> > option, any lookup of non existing file should result in calling
> > modprobe with filename as argument.
> > When coupled with mount tmpfs over /dev (or /udev) this functionality
> > would allow on-demand module loading (as with devfs and plain old
> > device nodes).
>
> How will you do the mapping of /dev names to modules in kernel space?
> How are you going to know which of the 50 or so sound drivers to load
> when opening /dev/dsp?
Just call modprobe. Modprobe will check /etc/modprobe.conf for dsp
aliases and load module. Then udev will make devnode.
> And what's wrong with the current scheme of, "load a driver when the
> device is seen"? This is how Linux currently works, and has been moving
> to for quite some time. In the past we didn't have that capability, so
> the "load the driver when we open the /dev node" hack was added.
Few days ago I did dd if=something of=/dev/floppy/0; then I saw
in logs that floppy module was loaded. That was because I use devfs
which run modprobe when it's needed.
With udev dd would fail with non-existant /dev/floppy/0. There
is no mechanism to call modprobe.
I'm also surprised that"load the driver when we open the /dev node"
is a hack. I get used to this standard Linux functionality as
something obvious. Other OSed (*BSD, Solaris etc.) don't work like
that?
--
Tomasz Torcz There exists no separation between gods and men:
zdzichu@irc.-nie.spam-.pl one blends softly casual into the other.
Please CC.
-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community? Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
_______________________________________________
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
next prev parent reply other threads:[~2003-10-25 1:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-25 0:00 On demand modules loading with {tmp,ram}fs and udev Tomasz Torcz
2003-10-25 0:42 ` Greg KH
2003-10-25 1:09 ` Tomasz Torcz [this message]
2003-10-28 18:31 ` Greg KH
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=marc-linux-hotplug-106704430028353@msgid-missing \
--to=zdzichu@irc.pl \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).