From: Martin Pitt <martin.pitt@ubuntu.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev rule file query
Date: Wed, 01 Sep 2010 15:25:42 +0000 [thread overview]
Message-ID: <20100901152542.GK2662@piware.de> (raw)
In-Reply-To: <002d01cb49e6$da8053e0$8f80fba0$@co.uk>
Hello Martin,
Martin Payne [2010-09-01 16:03 +0100]:
> So, I guess I should now use:
>
> SUBSYSTEM="usb", ATTR(idVendor)="1234"
Right, except that it's written ATTR{}, not ATTR().
> But will this work for older systems? It is not clear to me whether the
> SUBSYSTEM and ATTR keywords have been recognised by udev from the beginning.
Not from the beginning, but NEWS documents this pretty well:
---------------- 8< ----------------
udev 098
====
Bugfixes.
Renaming of some key names (the old names still work):
BUS -> SUBSYSTEMS, ID -> KERNELS, SYSFS -> ATTRS, DRIVER -> DRIVERS.
[...]
---------------- 8< ----------------
098 was released in August 2006, so in software terms SUBSYSTEM and
ATTR have been around for ages.
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
prev parent reply other threads:[~2010-09-01 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 15:03 udev rule file query Martin Payne
2010-09-01 15:25 ` Martin Pitt [this message]
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=20100901152542.GK2662@piware.de \
--to=martin.pitt@ubuntu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).