From: "Marco d'Itri" <md@Linux.IT>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 008 release
Date: Wed, 03 Dec 2003 23:59:56 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107049607719763@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107049067113625@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
On Dec 03, Greg KH <greg@kroah.com> wrote:
>I'm still looking for a devfs naming scheme config file. Can anyone
>verify that udev supports everything yet now or not? I know I've been
>saying this for a few releases now...
I'm attaching the one installed by default by the debian package.
It's not complete because some devices I own are not yet supported by
the kernel (notably sound cards, lp and input devices) and I do not know
the devfs names of some devices I do not own, but I will keep adding new
rules in the next weeks.
So far the only differences from devfs are the names of the cdrom
devices ("disc" intead of "cd") and the lack of symlinks in discs/ and
cdroms/.
--
ciao, |
Marco | [3447 peMS5jdXJiia.]
[-- Attachment #2: udev.rules --]
[-- Type: text/plain, Size: 1304 bytes --]
# There are a number of modifiers that are allowed to be used in the
# NAME or PROGRAM fields.
# They provide the following subsitutions:
# %n - the "kernel number" of the device.
# for example, 'sda3' has a "kernel number" of '3'
# %M - the kernel major number for the device
# %m - the kernel minor number for the device
# %b - the bus id for the device
# %c - the return value for the CALLOUT program (note, this doesn't work within
# the PROGRAM field for the obvious reason.)
# %D - use the devfs style disk name for this device.
# For partitions, this will result in 'part%n'
# If this is not a partition, it will result in 'disk'
#
NUMBER, BUS="ide", id="0.0", NAME="ide/host0/bus0/target0/lun0/%D"
NUMBER, BUS="ide", id="0.1", NAME="ide/host0/bus0/target1/lun0/%D"
NUMBER, BUS="ide", id="1.0", NAME="ide/host0/bus1/target0/lun0/%D"
NUMBER, BUS="ide", id="1.1", NAME="ide/host0/bus1/target1/lun0/%D"
REPLACE, KERNEL="md[0-9]*", NAME="md/%n"
REPLACE, KERNEL="tty[0-9]*", NAME="vc/%n"
REPLACE, KERNEL="ttyS[0-9]*", NAME="tts/%n"
REPLACE, KERNEL="ttyUSB[0-9]*", NAME="tts/USB%n"
REPLACE, KERNEL="video[0-9]*", NAME="v4l/video%n"
REPLACE, KERNEL="radio[0-9]*", NAME="v4l/radio%n"
REPLACE, KERNEL="vbi[0-9]*", NAME="v4l/vbi%n"
REPLACE, KERNEL="vtx[0-9]*", NAME="v4l/vtx%n"
next prev parent reply other threads:[~2003-12-03 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 22:29 [ANNOUNCE] udev 008 release Greg KH
2003-12-03 23:59 ` Marco d'Itri [this message]
2003-12-10 1:14 ` Greg KH
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=marc-linux-hotplug-107049607719763@msgid-missing \
--to=md@linux.it \
--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).