From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Does sysfs really provides persistent hardware path to devices?
Date: Sun, 18 Jan 2004 01:03:12 +0000 [thread overview]
Message-ID: <20040118010312.GA21384@vrfy.org> (raw)
In-Reply-To: <20040117213415.GB22238@kroah.com>
On Sat, Jan 17, 2004 at 01:34:16PM -0800, Greg KH wrote:
> On Sat, Jan 17, 2004 at 11:34:13PM +0300, Andrey Borzenkov wrote:
> > as example shows it probably can be done without serious patches. The only
> > problem is to make devpath available; at this point udev already computed it.
> > If you think it makes sense, patch will follow.
>
> I could see making devpath available as a % modifier.
It's available in the environment. PROGRAM="/bin/sh -c set>/tmp/set" shows:
ACTIONd
DEVPATH=/class/video4linux/video0
DIRSTACK=()
EUID=0
GROUPS=()
HOME=/
...
thanks,
Kay
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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:[~2004-01-18 1:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E19odOM-000NwL-00.arvidjaar-mail-ru@f22.mail.ru>
[not found] ` <200308311453.00122.arvidjaar@mail.ru>
[not found] ` <20030924211823.GA11234@kroah.com>
2004-01-17 20:34 ` Does sysfs really provides persistent hardware path to devices? Andrey Borzenkov
2004-01-17 21:34 ` Greg KH
2004-01-18 1:03 ` Kay Sievers [this message]
2004-01-18 14:05 ` Kay Sievers
2004-01-19 19:51 ` Greg KH
2004-03-14 19:25 ` Horst von Brand
2004-01-19 13:08 ` Olaf Hering
2004-01-19 13:59 ` Andries Brouwer
2004-01-19 14:04 ` Olaf Hering
2004-03-14 11:53 ` 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=20040118010312.GA21384@vrfy.org \
--to=kay.sievers@vrfy.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).