From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: I knew how to do this once...
Date: Fri, 17 Feb 2006 03:42:21 +0000 [thread overview]
Message-ID: <20060217034221.GB9749@kroah.com> (raw)
In-Reply-To: <200602160530.k1G5UTNG020004@deneb.dwf.com>
On Wed, Feb 15, 2006 at 10:30:29PM -0700, clemens@dwf.com wrote:
> How do you set up a rule, so that a module gets loaded
> whenever (or rather the first time) a file gets accessed.
>
> In this case it is /dev/ttyS0
Do you have CONFIG_KMOD enabled in your kernel? You also need to have
the /dev/ttyS0 (or whatever) device node created already when you do
this. udev will not automatically load the module if you try to open a
device node that isn't present (see the udev FAQ for why.)
> Also, If I need to load two modules, in a specific order,
> does referencing one in a rule cause the other to be loaded,
> or do I have to do some magic in the modprobe rules.
Is one module dependant on the other one? If so, modprobe will handle
it automatically. Otherwise, just put it in the file that your distro
uses to load modules at boot time, in the order you want it to be
loaded.
Hope this helps,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
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:[~2006-02-17 3:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 5:30 I knew how to do this once clemens
2006-02-17 3:42 ` Greg KH [this message]
2006-02-17 19:47 ` Reg Clemens
2006-02-17 22:09 ` 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=20060217034221.GB9749@kroah.com \
--to=greg@kroah.com \
--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).