From: mru@kth.se (Måns Rullgård)
To: linux-hotplug@vger.kernel.org
Subject: Re: udev/hotplug success story
Date: Sun, 08 Feb 2004 23:50:50 +0000 [thread overview]
Message-ID: <yw1xwu6xp1ut.fsf@kth.se> (raw)
In-Reply-To: <4026A5F4.1000901@reactivated.net>
Daniel Drake <dan@reactivated.net> writes:
> Hotplug is doing a good job of managing my usb modules. When I plug my
> camera in, it loads usb-storage as expected. However, it doesnt load
> sd_mod, meaning that no /dev/sda1 is created, and I can't access my
> pictures.
It used to load sd-mod automatically for me, but stopped some time
around 2.6.2-rc1.
> I could easily get around this by writing a script to "modprobe
> sd_mod", and then adding a line to /etc/hotplug/usb.usermap.
>
> To better fit in with the purpose of hotplugging, I would think that
> this module should be loaded automatically after usb-storage. Is this
> a bug/missing-feature, or intentional?
Hacking modprobe.conf to get that behavior is trivial.
--
Måns Rullgård
mru@kth.se
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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:[~2004-02-08 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 21:11 udev/hotplug success story Daniel Drake
2004-02-08 23:50 ` Måns Rullgård [this message]
2004-02-09 23:12 ` Patrick Mansfield
2004-02-13 1:38 ` Greg KH
2004-03-03 21:48 ` 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=yw1xwu6xp1ut.fsf@kth.se \
--to=mru@kth.se \
--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).