From: Yan Seiner <yan@seiner.com>
To: linux-hotplug@vger.kernel.org
Subject: NAME= silently fails
Date: Mon, 05 Nov 2007 13:45:02 +0000 [thread overview]
Message-ID: <472F1E5E.7060201@seiner.com> (raw)
I've been pulling my hair out over this seemingly simple issue.
I have a multi-head setup. With debian Etch, I used very simple udev
rules that assigned mice and keyboards to specific workstations.
I've upgraded to debian Lenny, and NAME= silently fails.
Old rule:
|SYSFS{phys}="usb-0000:00:10.0-1/input0", NAME="input/mouse10",
SYMLINK+="input/by-user/MouseJason", OPTIONS+="last_rule"|
SYSFS has apparently been deprecated in favor of ATTRS, so I rewrote the
rule:
ATTRS{phys}="usb-0000:00:02.0-1/input1", NAME="input/event10",
SYMLINK+="input/by-user/KbdYan", OPTIONS+="last_rule"
However the rule is silently ignored.
I've tried various combinations and as soon as I include NAME= then the
rule gets ignored.
If I just use a rule of the form
KERNEL="mouse*|js*", ENV{ID_PATH}="pci-0000:00:02.0-usb-0:2:1.0", \
SYMLINK+="input/by-user/KYanMouse"
it works fine, but if I modify it to include
KERNEL="event*", ENV{ID_PATH}="pci-0000:00:02.0-usb-0:1:1.0", \
SYMLINK+="input/by-user/YanKbd", \
NAME+="input/YanKbd"
then it fails.
Can someone please clue me in? xorg's evdev driver will not accept
symlinks, and I can't get my dual head workstations going....
Thanks,
--Yan
-------------------------------------------------------------------------
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-11-05 13:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=472F1E5E.7060201@seiner.com \
--to=yan@seiner.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.