From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Adam Kropelin" Date: Fri, 03 Aug 2007 17:04:54 +0000 Subject: Re: Static naming for hiddev nodes Message-Id: <03eb01c7d5f0$69983ac0$03c8a8c0@kroptech.com> List-Id: References: <01fe01c7d561$6a20b1a0$03c8a8c0@kroptech.com> In-Reply-To: <01fe01c7d561$6a20b1a0$03c8a8c0@kroptech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org Kay Sievers wrote: > On 8/3/07, Adam Kropelin wrote: >> Kay Sievers wrote: >>> Does: >>> KERNEL="hiddev*", SYSFS{serial}="BB0100009999", NAME="ups" >>> work? >> >> Perfectly. >> >> It is interesting, looking at the udevinfo output, to see that the >> device with DRIVER="usbhid" has no SYSFS{serial}...which explains >> why that particular permutation of the rule did not work. > > It should still have worked, maybe there are timing problems. In > general its better to match directly on a device property of the > device you want to hook into, like "hiddev*" is doing. That way, you > will never catch any of the parent events, only check for the > properties of the parents starting at the right event. Makes sense now. > It may also be better to create just a symlink, because the kernel log > will report errors with the kernel name and you have no easy way to > tell which of your names belong to which kernel device. Good point. I'll make that change. --Adam ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ 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