From: Scott James Remnant <scott@canonical.com>
To: linux-hotplug@vger.kernel.org
Subject: Patches for device names
Date: Wed, 13 Aug 2008 17:22:55 +0000 [thread overview]
Message-ID: <1218648175.6882.63.camel@quest> (raw)
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
Before I get patching, I wanted to get a consensus about what the best
patches would be, since there's a few options:
a) kernel names match LANANA, using ! instead of /
ACTION=add
DEVPATH=/class/input/mice
SUBSYSTEM=input
MAJOR=13
MINOR=63
Pro: simplest, ! -> / already supported by udev
Con: looks strange in sysfs;
/class/input/mice becomes /class/input/input!mice;
backwards compatibility?
- we can match NAME=="input/mice" for permissions,
this works for both!
b) kernel names remain the same, include DEVNAME in environment
ACTION=add
DEVPATH=/class/input/mice
DEVNAME=/dev/input/mice
SUBSYSTEM=input
MAJOR=13
MINOR=63
Pro: fixes sysfs and compatibility, attractive
Con: udev needs patching, extra macro in kernel
Scott
--
Scott James Remnant
scott@canonical.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2008-08-13 17:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 17:22 Scott James Remnant [this message]
2008-08-13 17:31 ` Patches for device names H. Peter Anvin
2008-08-13 17:49 ` Greg KH
2008-08-13 17:50 ` Greg KH
2008-08-13 17:57 ` Scott James Remnant
2008-08-13 18:02 ` Scott James Remnant
2008-08-13 18:16 ` Greg KH
2008-08-13 18:22 ` H. Peter Anvin
2008-08-13 18:33 ` Scott James Remnant
2008-08-13 18:38 ` David Zeuthen
2008-08-13 18:52 ` Kay Sievers
2008-08-13 18:54 ` Kay Sievers
2008-08-13 19:33 ` Scott James Remnant
2008-08-13 20:00 ` H. Peter Anvin
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=1218648175.6882.63.camel@quest \
--to=scott@canonical.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).