From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Fri, 12 Mar 2004 00:49:55 +0000 Subject: Re: modprobe before udevstart Message-Id: <20040312004954.GA27271@kroah.com> List-Id: References: <200403100928.53010.bobb@absamail.co.za> In-Reply-To: <200403100928.53010.bobb@absamail.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Wed, Mar 10, 2004 at 09:28:53AM +0200, Bob Barry wrote: > I have the usual rule for loop devices in my udev.rules, but loop > devices were not getting created at startup because the loop entries > were not yet in sysfs. Re-running the "populate_udev" script, or > udevstart, after the system was running, created the devices OK. > Devices associated with ALSA sound and LTmodem behaved similarly. > Putting an "autoload modules" loop into the startup script (rc in Gentoo) > ahead of "populate_udev" (or udevstart) made it work properly for me. > Is "modprobe essential modules before udevstart" desireable or > acceptable practice? It shouldn't be necessary at all. It works for me without it, I really don't understand why it wouldn't for you. thanks, greg k-h ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click _______________________________________________ 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