From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Fri, 17 Feb 2006 03:42:21 +0000 Subject: Re: I knew how to do this once... Message-Id: <20060217034221.GB9749@kroah.com> List-Id: References: <200602160530.k1G5UTNG020004@deneb.dwf.com> In-Reply-To: <200602160530.k1G5UTNG020004@deneb.dwf.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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&kid3432&bid#0486&dat1642 _______________________________________________ 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