From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Kay Sievers" <kay.sievers@vrfy.org>
Date: Fri, 03 Aug 2007 00:59:57 +0000
Subject: Re: Static naming for hiddev nodes
Message-Id: <3ae72650708021759l68518f56lc9ab95d95948685b@mail.gmail.com>
List-Id: <linux-hotplug.vger.kernel.org>
References: <01fe01c7d561$6a20b1a0$03c8a8c0@kroptech.com>
In-Reply-To: <01fe01c7d561$6a20b1a0$03c8a8c0@kroptech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
To: linux-hotplug@vger.kernel.org

On 8/3/07, Adam Kropelin <akropel1@rochester.rr.com> wrote:
> Kay Sievers wrote:
> > On 8/3/07, Adam Kropelin <akropel1@rochester.rr.com> wrote:
> >> I'm attempting to establish static naming for some hiddev devices
> >> (UPSes) based on serial numbers. I used to be able to do this fairly
> >> easily many moons ago in the early days of udev. Revisiting it on a
> >> modern distro (RHEL5) I am unable to make it work. Here are the udev
> >> rules I've tried and what happened with each....
> >>
> >>     DRIVER=3D"hiddev", SYSFS{serial}=3D"JB0319039999", NAME=3D"ups1"
> >>     - Does not match
> >>
> >>     DRIVER=3D"usbhid", SYSFS{serial}=3D"JB0319039999", NAME=3D"ups1"
> >>     - Does not match
> >>
> >>     SYSFS{serial}=3D"JB0319039999", NAME=3D"ups1"
> >>     - Matches, but results in a device node for the usbdev not for
> >> the hiddev
> >>
> >>     BUS=3D"usb", SYSFS{serial}=3D"JB0319039999", NAME=3D"ups1"
> >>     - Matches, but results in a device node for the usbdev not for
> >> the hiddev
> >>
> >>     SUBSYSTEM=3D"usb", SYSFS{serial}=3D"JB0319039999", NAME=3D"ups1"
> >>     - Does not match
> >>
> >> I admit to being almost completely lost in the sysfs hierarchy. I'd
> >> be happy to post a subtree if someone can suggest which one would be
> >> helpful. It is worth noting that the default rules create correct and
> >> working hiddev* nodes...I'm just trying to given them persistent
> >> names.
> >
> > What is the "original" device node name, you expect and want to
> > rename?
>
> hiddev0
>
> > What does:
> >  udevmonitor --env --kernel
> > print when you connect the device?
>
> My udevmonitor does not appear to support the --kernel option, but here
> is output from --env:

> UDEV  [1186101575.338918] add@/class/usb/hiddev0
> UDEV_LOG=3D3
> ACTION=ADd
> DEVPATH=3D/class/usb/hiddev0
> SUBSYSTEM=3Dusb
> SEQNUM(33
> PHYSDEVPATH=3D/devices/pci0000:00/0000:00:07.2/usb1/1-2/1-2.3/1-2.3:1.0
> PHYSDEVBUS=3Dusb
> PHYSDEVDRIVER=3Dusbhid
> MAJOR=180
> MINOR=96
> UDEVD_EVENT=3D1
> DEVNAME=3D/dev/hiddev0

What does:
  udevinfo -a -p /class/usb/hiddev0
print?

Kay

-------------------------------------------------------------------------
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