From: DervishD <udev@dervishd.net>
To: linux-hotplug@vger.kernel.org
Subject: Loading modules on demand with /sbin/hotplug
Date: Tue, 27 Feb 2007 17:23:20 +0000 [thread overview]
Message-ID: <20070227172320.GA10176@DervishD> (raw)
Hi all :))
First of all, if this is not the proper forum, please ignore my
message and point me to the proper place/information source, please ;)
Well, I'm setting up hotplugging by hand on a do-it-yourself Linux
box, and until now everything has worked ok: udev is up and running, and
succesfully creates/removes dev entries, the dynamic /dev is usable too
with a 2.4 kernel by some booting tricks and udevd runs fast.
My next step is to automatically create mount points and load needed
modules as soon as some devices are plugged into the system. Here is
where I need some advice, because none of my approaches have worked
100%.
Since I would like to avoid things like HAL and the like, my first
try was to use the "RUN" key, containing a script that creates mount
points and loads modules. The script, run by hand, works like a charm.
Unfortunately, I was having problems getting the remove events, since I
was filtering by "ATTRS{serial}" and at removing time, the parent device
(which contained that information) was removed before the "final" device
(that is, the one that caused the /dev entry using "NAME").
Trying to find a correct combination of keys to filter seemed
difficult and so I tried a different approach. This time I put my script
as /sbin/hotplug instead of having it in a "RUN" key. Here my problem is
that I cannot get the information properly in my script.
Well, long story short: assuming that I have udev up and running,
and a script capable of creating mount points and load modules (right
now, using a config file, in the future I may use MODALIAS or something
like that, if I'm able to get a grip on it), how the heck should I write
rules/set up things so my script is called and able to perform its duty?
Thanks a lot, and sorry if this question has been answered before,
I've took a look at the FAQ and I didn't find anything useful, and a
couple of search of the mailing list archives didn't give any info,
either.
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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 reply other threads:[~2007-02-27 17:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 17:23 DervishD [this message]
2007-02-27 17:45 ` Loading modules on demand with /sbin/hotplug DervishD
2007-02-27 19:16 ` Kay Sievers
2007-02-27 20:17 ` DervishD
2007-02-28 12:45 ` DervishD
2007-02-28 15:36 ` Kay Sievers
2007-02-28 19:26 ` Dan Nicholson
2007-02-28 22:02 ` DervishD
2007-02-28 22:05 ` DervishD
2007-02-28 22:20 ` Kay Sievers
2007-03-01 8:42 ` DervishD
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=20070227172320.GA10176@DervishD \
--to=udev@dervishd.net \
--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).