From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug in latest udev
Date: Sat, 05 Feb 2005 13:29:46 +0000 [thread overview]
Message-ID: <1107610186.5494.41.camel@localhost.localdomain> (raw)
In-Reply-To: <e7963922050205051668922de0@mail.gmail.com>
On Sat, 2005-02-05 at 14:16 +0100, Stefan Schweizer wrote:
> Hi,
>
> the latest udev release has a bug in the rules file:
> # alsa devices
> KERNEL="controlC[0-9]*", NAME="snd/%k", GROUP="audio"
> KERNEL="hw[CD0-9]*", NAME="snd/%k", GROUP="audio"
> KERNEL="pcm[CD0-9cp]*", NAME="snd/%k", GROUP="audio"
> KERNEL="midiC[D0-9]*", NAME="snd/%k", GROUP="audio"
> KERNEL="timer", NAME="snd/%k", GROUP="audio"
This file is just an example and not every time up to date. The
individual distribution rules files need to catch up now, so I wouldn't
call this a "bug".
And you may use a "subsystem only"-rule for that:
SUBSYSTEM="sound", GROUP="audio"
This will apply to all your audio devices if you don't specify any other
GROUP with the individual rules.
Ah, and please be more specific in the Subject of the mail.
Thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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
next prev parent reply other threads:[~2005-02-05 13:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-05 13:16 Bug in latest udev Stefan Schweizer
2005-02-05 13:29 ` Kay Sievers [this message]
2005-02-05 14:03 ` Stefan Schweizer
2005-02-05 14:05 ` Marco d'Itri
2005-02-05 14:24 ` Kay Sievers
2005-02-05 14:40 ` Stefan Schweizer
2005-02-05 15:42 ` Kay Sievers
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=1107610186.5494.41.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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).