From: Moshe Yudkowsky <msha5_17@bl.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: action does not trigger on remove, only on add
Date: Tue, 28 Mar 2006 19:08:05 +0000 [thread overview]
Message-ID: <44298995.4040401@bl.com> (raw)
In-Reply-To: <442979C9.9090908@bl.com>
> This never worked, cause there are no sysfs files to match against
> when the device is gone.
OK, it must have been some previous script that worked on unplug. What
would be the correct way -- the recommended, best-practices way -- to
match on unplug, if I match on a SYSFS variable on plugin?
If udevmonitor shows:
> ID_VENDOR=iriver
> ID_MODEL=MassStorage_Disc
> ID_REVISION\001
> ID_SERIAL=iriver_MassStorage_Disc
> ID_TYPE=disk
> ID_BUS=usb
then in what way is ID_VENDOR accessible to a script?
I could set an ENV variable on plugin and then match it again at
unplug, I suppose. But is there a better method? ENV is a bit difficult
to work with because it doesn't accept %p and similar variables to set.
While I can certainly code a solution that fixes just this problem, I
prefer broader solutions.
Here's a plea for some slight changes in the output format for
udevmonitor. One problem I always have whenever I sit down to work with
udev is matching the output of udevmonitor with the various variables
mentioned in the documentaion. I.e., the output of udevmonitor shows
ID_PATH, and that'd be a fine key to match against. Is ID_PATH the same
as %p? No, but then what is this ID_KEY? What line in udevmonitor's
output matches to %id as mentioned in the man page? MAJOR and MINOR are
easy enough, but all these others can be a real puzzle -- even though
the information is right there in udevmonitor's output. udevinfo seems a
lot better about showing what's sysfs{}, and that's a big help.
--
Moshe Yudkowsky
work: http://www.Disaggregate.com
book: http://www.PebbleAndAvalanche.com
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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
prev parent reply other threads:[~2006-03-28 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 18:00 action does not trigger on remove, only on add Moshe Yudkowsky
2006-03-28 18:05 ` Kay Sievers
2006-03-28 19:08 ` Moshe Yudkowsky [this message]
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=44298995.4040401@bl.com \
--to=msha5_17@bl.com \
--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).