All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Adam Kropelin" <akropel1@rochester.rr.com>
To: linux-hotplug@vger.kernel.org
Subject: Static naming for hiddev nodes
Date: Fri, 03 Aug 2007 00:01:17 +0000	[thread overview]
Message-ID: <01fe01c7d561$6a20b1a0$03c8a8c0@kroptech.com> (raw)

Hi all,

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="hiddev", SYSFS{serial}="JB0319039999", NAME="ups1"
    - Does not match

    DRIVER="usbhid", SYSFS{serial}="JB0319039999", NAME="ups1"
    - Does not match

    SYSFS{serial}="JB0319039999", NAME="ups1"
    - Matches, but results in a device node for the usbdev not for the 
hiddev

    BUS="usb", SYSFS{serial}="JB0319039999", NAME="ups1"
    - Matches, but results in a device node for the usbdev not for the 
hiddev

    SUBSYSTEM="usb", SYSFS{serial}="JB0319039999", NAME="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.

Thanks in advance for any suggestions...
--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

             reply	other threads:[~2007-08-03  0:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03  0:01 Adam Kropelin [this message]
2007-08-03  0:12 ` Static naming for hiddev nodes Kay Sievers
2007-08-03  0:44 ` Adam Kropelin
2007-08-03  0:59 ` Kay Sievers
2007-08-03  1:11 ` Adam Kropelin
2007-08-03  1:29 ` Kay Sievers
2007-08-03 12:12 ` Adam Kropelin
2007-08-03 14:10 ` Kay Sievers
2007-08-03 17:04 ` Adam Kropelin

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='01fe01c7d561$6a20b1a0$03c8a8c0@kroptech.com' \
    --to=akropel1@rochester.rr.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.