From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Sun, 18 Jan 2004 14:05:18 +0000 Subject: Re: Does sysfs really provides persistent hardware path to devices? Message-Id: <20040118140518.GA22757@vrfy.org> List-Id: References: <20040117213415.GB22238@kroah.com> In-Reply-To: <20040117213415.GB22238@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org On Sun, Jan 18, 2004 at 02:03:12AM +0100, Kay Sievers wrote: > 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=20 > > > problem is to make devpath available; at this point udev already comp= uted it.=20 > > > If you think it makes sense, patch will follow. > >=20 > > I could see making devpath available as a % modifier. >=20 > It's available in the environment. PROGRAM=3D"/bin/sh -c set>/tmp/set" sh= ows: >=20 > ACTION=ADd > DEVPATH=3D/class/video4linux/video0 > DIRSTACK=3D() > EUID=3D0 > GROUPS=3D() > HOME=3D/ > ... Oh, sorry, better to read the whole text :) You mean the "device" path, right? 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