From: Moshe Yudkowsky <moshe@pobox.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Why not picking up ENV variables?
Date: Sun, 02 Apr 2006 19:48:19 +0000 [thread overview]
Message-ID: <44302A83.7020503@pobox.com> (raw)
In-Reply-To: <442FD482.5000707@bl.com>
> Unless I misread the code, stored environment is not available when matching
> device event; it is imported after that, immediately before RUN programs are
> going to be run. As most other callouts are run only on ACTION="add", it
> means environment is mostly not available for remove rules.
I will certainly try to find time to run against this patch. Is there a
"best practices" method for "remove" events? If sysfs isn't available,
and I can't import to the environment via path_id, then what's left to
match against?
--
Moshe Yudkowsky * moshe@pobox.com * www.pobox.com/~moshe
"The odds are good, but the goods are odd."
-- Alaskan women, on the high ratio of men to women in Alaska
-------------------------------------------------------
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
next prev parent reply other threads:[~2006-04-02 19:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 13:41 Why not picking up ENV variables? Moshe Yudkowsky
2006-04-02 14:58 ` Moshe Yudkowsky
2006-04-02 16:47 ` Andrey Borzenkov
2006-04-02 19:48 ` Moshe Yudkowsky [this message]
2006-04-04 11:20 ` Moshe Yudkowsky
2006-04-04 16:31 ` Andrey Borzenkov
2006-04-04 17:40 ` Moshe Yudkowsky
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=44302A83.7020503@pobox.com \
--to=moshe@pobox.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).