From: iSteve <isteve@rulez.cz>
To: linux-hotplug@vger.kernel.org
Subject: Linux 2.4 hotplug interface bus information
Date: Wed, 20 Sep 2006 15:09:58 +0000 [thread overview]
Message-ID: <20060920170958.57c0ae80@silver> (raw)
Greetings,
I'm looking at hotplug event interface on 2.4 kernels (testbed is vanilla
2.4.32), and I wonder how did the old hotplug shell script system figured out
what bus the device is connected to. I've hooked up a script that dumps env
vars to a file to /proc/sys/kernel/hotplug, and when connecting and removing
some MicroStar Bluetooth device, I get only these events:
PATH=/sbin:/bin:/usr/sbin:/usr/bin
ACTIONd
PWD=/
SHLVL=1
HOME=/
PRODUCTÛ0/6970/525
TYPE"4/1/1
_=/usr/bin/env
PATH=/sbin:/bin:/usr/sbin:/usr/bin
ACTION=remove
PWD=/
SHLVL=1
HOME=/
PRODUCTÛ0/6970/525
TYPE"4/1/1
_=/usr/bin/env
I'd like to write a dumb function that would generate modalias out of these (or
further process them in any fashion), but without the bus, I believe I can
never succeed.
Thanks in advance for any reply.
--
-- iSteve
-------------------------------------------------------------------------
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:[~2006-09-20 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 15:09 iSteve [this message]
2006-09-20 15:57 ` Linux 2.4 hotplug interface bus information iSteve
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=20060920170958.57c0ae80@silver \
--to=isteve@rulez.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.