linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Torcz <zdzichu@irc.pl>
To: linux-hotplug@vger.kernel.org
Subject: On demand modules loading with {tmp,ram}fs and udev
Date: Sat, 25 Oct 2003 00:00:18 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-106704029925575@msgid-missing> (raw)

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).

On #kernelnewbies I was told to use ramfs (as device nodes don't have
to be swap bakced). But it looks like polluting simple ramfs
with this mount option is not good. Is using tmpfs OK?

please cc me on comments.
-- 
Tomasz Torcz            There exists no separation between gods and men:
zdzichu@irc.-nie.spam-.pl   one blends softly casual into the other. 
|> Playing:  ...


-------------------------------------------------------
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

             reply	other threads:[~2003-10-25  0:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-25  0:00 Tomasz Torcz [this message]
2003-10-25  0:42 ` On demand modules loading with {tmp,ram}fs and udev Greg KH
2003-10-25  1:09 ` Tomasz Torcz
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-106704029925575@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).