From: Richard Michael <rmichael-hotplug@edgeofthenet.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: ENV{DEVNAME} in remove rule?
Date: Tue, 03 Jul 2007 17:52:38 +0000 [thread overview]
Message-ID: <20070703175238.GI27375@server> (raw)
In-Reply-To: <20070703171658.GB27375@server>
> DEVNAME is set by udev before calling RUN programs. It is not available when
> rules are being processed.
Where are these details documented? I've been writing lots of test
rules to try and figure this out, but I'd prefer to just read something.
> In general I am not sure it is wise to match on DEVNAME It can be changed at
> any time by installing different rule(s). Better to match on device
> properties.
I'd really prefer to match PHYSDEVPATH, because what I actually care
about is identifying the USB socket which the device is attached
(especially for the "add" rule.. the "remove" just uses the device name
as I set it when it was added). However, PHYSDEVPATH has been
deprecated.
I want to create block devices (not symlinks) for the specific ports of
a USB (or firewire) controller, and take actions depending on which
socket of the controller has been used.
Thanks,
Richard
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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:[~2007-07-03 17:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 17:16 ENV{DEVNAME} in remove rule? Richard Michael
2007-07-03 17:45 ` Andrey Borzenkov
2007-07-03 17:52 ` Richard Michael [this message]
2007-07-03 18:06 ` Andrey Borzenkov
2007-07-03 18:17 ` Richard Michael
2007-07-03 19:44 ` Andrey Borzenkov
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=20070703175238.GI27375@server \
--to=rmichael-hotplug@edgeofthenet.org \
--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).