linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bob Barry <bobb@absamail.co.za>
To: linux-hotplug@vger.kernel.org
Subject: modprobe before udevstart
Date: Wed, 10 Mar 2004 07:28:53 +0000	[thread overview]
Message-ID: <200403100928.53010.bobb@absamail.co.za> (raw)

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?


-------------------------------------------------------
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_id\x1470&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

             reply	other threads:[~2004-03-10  7:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-10  7:28 Bob Barry [this message]
2004-03-12  0:49 ` modprobe before udevstart 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=200403100928.53010.bobb@absamail.co.za \
    --to=bobb@absamail.co.za \
    --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).